Skip to content

Commit c4c1ddf

Browse files
mmahacekjeffgdotorgjeremystretch
authored
14660: Update webhook docs (#14661)
* 14660: Update webhook docks * Update docs/integrations/webhooks.md Co-authored-by: Jeff Gehlbach <[email protected]> * #14660: Doc note about webhook receiver on Docker * Cleanup & remove Docker reference (out of scope for docs) --------- Co-authored-by: Jeff Gehlbach <[email protected]> Co-authored-by: Jeremy Stretch <[email protected]>
1 parent 3645bd7 commit c4c1ddf

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

docs/integrations/webhooks.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -106,6 +106,6 @@ Content-Type: application/x-www-form-urlencoded
106106
------------
107107
```
108108

109-
Note that `webhook_receiver` does not actually _do_ anything with the information received: It merely prints the request headers and body for inspection.
109+
Note that `webhook_receiver` does not actually _do_ anything with the information received: It merely prints the request headers and body for inspection. If you don't see any output, check that the `rqworker` process is running and that webhook events are being placed into the queue.
110110

111-
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 (visible under the NetBox admin UI).
111+
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 log for failed webhooks.

0 commit comments

Comments
 (0)