- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Meraki Webhooks don't seem to be triggering?
I can push alerts from the postman collection through just fine, as well as the test event sent by the "send test webhook" button in the alert configuration page, but try as I might I can't get any *actual* events to come through. Ripping cables in/out, graceful reboots, power cycling, combinations of the above including or not including the spare to trigger failovers, etc.
Events will show up in the event log for the correct network:
And I've tried enabling literally every checkbox in the alarm page
But I can't seem to get a response. Any ideas of what I could be missing?
Also, webhook function is marked "Beta". How "Beta" is "Beta"? Should I even be contemplating using this to monitor production networks?
Solved! Go to solution.
- Labels:
-
Webhooks
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Solution came from Meraki support:
I had defined the webhooks, but hadn't actually added the webhooks to the "default recipient list" as described in the docs here: https://documentation.meraki.com/zGeneral_Administration/Cross-Platform_Content/Alerts_and_Notificat...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
And to be clear: When I say it's not sending alerts, I'm going off of logs from the actual webhook handler itself, and no HTTPS session is being created at all for real events (but "send test webhook" works fine, etc)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Are you using a public SSL certificate?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
yep. implementation detail is that this is fronted by Amazon API Gateway service. For *now* it's just using the randomly generated domain names they give you, and that all comes w/ solid certs. Ultimately I'll be replacing that w/ a custom domain, but testing it as-is for now. And in any case if the issue was related to that I'd have expected the "test webhook" button to fail as well, though who knows.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
As a really quick test to ensure Meraki is sending the alerts, try using this test service to troubleshoot.
If you receive alerts using the provided https url, then you can focus on troubleshooting your receiver setup.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Great idea!
Still no luck using that site however.
the "test webhook" button works fine, but all other attempts to trigger an alert fail.
Things I've tried:
* Cable pulls, power cycles etc
* Trying right after applying the settings, and also 30 minutes later
* Made sure (again) that the devices I'm messing with are in the same network I applied the alert settings to
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Solution came from Meraki support:
I had defined the webhooks, but hadn't actually added the webhooks to the "default recipient list" as described in the docs here: https://documentation.meraki.com/zGeneral_Administration/Cross-Platform_Content/Alerts_and_Notificat...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
This post helped me fix my problem, but I couldn't find where it said to add the WebHook to 'Default Recipient List' in the pinned Meraki KB. I'm assuming the KB has been updated...
I did find it here tho:
