NeoAnd/netbox
1
0
Fork 0
mirror of https://github.com/netbox-community/netbox.git synced 2025-08-18 05:28:16 -06:00
Code Issues Actions 4 Packages Projects Releases Wiki Activity

Update docs/integrations/webhooks.md

Browse Source 
Co-authored-by: Jeff Gehlbach <jeffg@jeffg.org>
This commit is contained in:
mmahacek 2024-01-03 11:44:12 -08:00 committed by GitHub
parent 7821519a18
commit f4344d7f9b
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
docs/integrations/webhooks.md
View File

@ -109,5 +109,5 @@ Content-Type: application/x-www-form-urlencoded
Note that `webhook_receiver` does not actually _do_ anything with the information received: It merely prints the request headers and body for inspection. Note that `webhook_receiver` does not actually _do_ anything with the information received: It merely prints the request headers and body for inspection.
Now, when the NetBox webhook is triggered and processed, you should see its headers and content appear in the terminal where the webhook receiver is listening. If you don't, check that the `rqworker` process is running and that webhook events are being placed into the queue. Now, when the NetBox webhook is triggered and processed, you should see its headers and content appear in the terminal where the webhook receiver is listening. If you don't, check that the `rqworker` process is running and that webhook events are being placed into the queue.
Webhook results can be found in the NetBox admin UI under the Background Tasks section. Webhook results can be found in the NetBox admin UI under the Background Tasks section. Webhook results can be found in the NetBox admin UI under the Background Tasks section.
You can see any finished or failed runs, as well as the error stack if the webhook failed. You can see any finished or failed runs, as well as the error stack if the webhook failed.