Does anyone have better documentation on it? very vague, i see 0.0.0.0 listening on port 6000 but not sure what the URL if any for the sensor is. trying to setup webhook url from netbox to st2
This site is in read only mode. Please continue to browse, but replying, likes, and other actions are disabled for now.
⚠️ We've moved!
Hi there!
To reduce project dependency on 3rd party paid services the StackStorm TSC has decided to move the Q/A from this forum to Github Discussions. This will make user experience better integrated with the native Github flow, as well as the questions closer to the community where they can provide answers.
Use 🔗 Github Discussions to ask your questions.
Look at this section:
Based on your desired settings, the URL for the webhook’s configuration inside of NetBox will be:
http://<ip-address>:<port>/netbox/webhooks/
tried, api logs dont show anything
Replies back with
Nope
Which API logs? It’s not going to be st2api, it’s going to be the sensor
The sensor does not pic it up
What does “The sensor does not pic it up” mean?
Sorry pick it up, nothing incoming. fw is off on the box and url is correct in netbox. http://serverip:port/netbox/webhooks/
Start with the basics - do you see inbound traffics from the netbox server?
i will run some tcpdumps on each end
Got webhooks to work by doing the following and running upgrade again
sudo -H pip3 install django-rest-swagger django-rq psycopg2
sudo apt-get install python3-psycopg2
sudo -H ./upgrade.sh
helped resolve webhooks but i am not able to see anything in the list of what to monitor on changes etc . did the image come through?
You’ll need to check the netbox docs to see what webhooks they send
running below cmd i dont see any queue started when creating or deleting an item. does a webhook goto ->redis (rq) -> destination ?
rq info --interval 1
Why are you using rq commands?
Correct, I have and doesnt show the flow. IF reddis is suppose to pickup the job its not working
https://netbox.readthedocs.io/en/latest/additional-features/webhooks/
no queues are run, and the webhook is sent but no payload. and again - the list i sent of available triggers are maybe 10 , where as the older ver of netbox shows all. connection, interface, etc
b/c i used the admin/webhook-backend-status/
0 queues, etc
1 worker, no old jobs or failed
Wow disregard ALL my msgs in this thread. i thought these were going to the netbox list! sorry!!
Ah, no worries! I wondered if it was something like that. Easy mistake when you’re switching between a couple of lists