From c4c1ddf68dae90cd0e972ce0f41d20bdb6fed72c Mon Sep 17 00:00:00 2001 From: mmahacek Date: Wed, 10 Jan 2024 12:20:36 -0800 Subject: [PATCH] 14660: Update webhook docs (#14661) * 14660: Update webhook docks * Update docs/integrations/webhooks.md Co-authored-by: Jeff Gehlbach * #14660: Doc note about webhook receiver on Docker * Cleanup & remove Docker reference (out of scope for docs) --------- Co-authored-by: Jeff Gehlbach Co-authored-by: Jeremy Stretch --- docs/integrations/webhooks.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/integrations/webhooks.md b/docs/integrations/webhooks.md index 8913fd99c..20e9bc8c0 100644 --- a/docs/integrations/webhooks.md +++ b/docs/integrations/webhooks.md @@ -106,6 +106,6 @@ 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. If you don't see any output, 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 (visible under the NetBox admin UI). +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.