webhooks as an event destination don't support headers?

[scott_f]

It seems like a big oversight not to allow headers in webhook notifications. Headers often contain essential information like tokens to make the POST call. Also, per the documentation the payload is in XML (1990's called...).

If anyone is on here from NetApp, are improvements to 1) allow custom headers and 2) make the payload JSON coming to ONTAP webhooks? The current implementation is unworkable integrating with things like Splunk.

[AlexDawson · Accepted solution]

Thanks for your feedback. At this time, we support client certifications for authentication to webhook endpoints, as detailed at https://docs.netapp.com/us-en/ontap/error-messages/configure-webhooks-event-notifications-task.html#configure-a-webhook-destination-to-use-https-with-...

I would assume you can also do a URI which includes credentials for simple auth. Not a splunk guru, but would either of these do what you need?

To request a feature such as you've outlined above, please contact your account team to lodge an RFE BURT. 

Thanks!

[scott_f]

Thanks for the reply. Splunk does have an option (allowQueryStringAuth) to allow the HEC token to be embedded in the endpoint as a query, but our implementation does not have this enabled so we can't use it.  Other competitors I have seen are using curl under the hood, so as long as we can construct a working curl syntax that makes it very flexible.  But XML will still be a pain to deal with whereas JSON would be a piece of cake for Splunk.  I'll have out account team create an RFE on our behalf.