Unified Assurance (MOSC)

MOSC Banner

webhook aggregator fails to parse "content-type: application/json; charset:utf-8" into a Perl hash

edited 3:51PM in Unified Assurance (MOSC)

I've opened up a support request on this but posting here in case it helps others. We recently created some webhook parsing rules for events sourcing from Datadog. After some testing, we were able to see the $content object seemed to be JSON instead of the usual Perl hash suggesting the webhook aggregator service failed to parse the incoming payload.

After some investigation, the current theory is alerts with "Content-Type: application/json; charset=utf-8" are not being detected by the service as JSON and do not get decoded into the Perl $content hash. According to the Mozilla developer docs, this is a perfectly acceptable way for a source system to send JSON. That documentation can be found here https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Headers/Content-Type.

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month

New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center