Organization Webhook Payload Templates and Http Servers - UI missing, assignment not working

SOLVED
david_n_m_bond
Building a reputation

Organization Webhook Payload Templates and Http Servers - UI missing, assignment not working

I can create, update and delete Organization-level (as opposed to Network-level) Webhook Payload Templates and corresponding HTTP Servers.

 

Two critical issues:

  1. There seems to be no UI for these at the organization level, despite a links that claims to go to "Configure organization-wide alerts at Organization > Settings" on the Network's Alert Settings page.
  2. When assigning Http Servers to the network, no error is returned, but assignment fails and a subsequent fetch of a network's alert settings yields no HttpServers
  3. I am not receiving any alerts at the HTTP Server

Is this functionality working AT ALL, or is the advice "use per-network PayloadTemplates and HttpServers for now"?

Author, https://www.nuget.org/packages/Meraki.Api/
1 ACCEPTED SOLUTION
Ryan_Miles
Meraki Employee
Meraki Employee

If you're talking about this webhook endpoint https://developer.cisco.com/meraki/api-v1/get-organization-webhooks-http-servers/ it only pertains to Meraki Insight. 

 

Standard webhook templates are network level only today.

View solution in original post

2 REPLIES 2
Ryan_Miles
Meraki Employee
Meraki Employee

If you're talking about this webhook endpoint https://developer.cisco.com/meraki/api-v1/get-organization-webhooks-http-servers/ it only pertains to Meraki Insight. 

 

Standard webhook templates are network level only today.

Thanks @Ryan_Miles - that explains a lot!

 

I was hoping that I could define:

  • a single Webhook Template
  • a single HTTP Server

...and assign these to all networks' alert settings.

 

Instead, we have to create thousands of identical duplicates for each network.

 

It seems odd, because the "out of the box" templates ARE centralised, (Microsoft Teams, for example).  Surely it would make sense to allow the organization-level webhook templates to be used?  This would involve no UI change other than extending the list dropdown.

 

Similarly, it would make sense to permit users to use centralised HTTP Servers, to avoid having to re-enter credentials every time a network is added.

Author, https://www.nuget.org/packages/Meraki.Api/
Get notified when there are additional replies to this discussion.
Welcome to the Meraki Community!
To start contributing, simply sign in with your Cisco account. If you don't yet have a Cisco account, you can sign up.