Alerts - Possibility to add additional data to the payload/json

[Angelodaniel]

Problem Statement

In Splunk Observability Cloud, each detector have the possibility to customize the message that you send over the webhook if possible for more integrations. The Tip field becomes part of the json body sent.

So we need to have webhook integration where we can add the header, and per alert where we can add key-value pairs.

We want to be able to configure more on the webhook, just like some extra options for the Slack integration.

Solution Brainstorm

Product Area

Alerts

┆Issue is synchronized with this Jira Improvement by Unito

[getsantry[bot]]

Assigning to @getsentry/support for routing ⏲️

[getsantry[bot]]

Routing to @getsentry/product-owners-alerts for triage ⏲️

[sepbehroozi]

I assume the suggested red box would accept Custom Tags, like the slack integration. right? If so, that solves most of our need at Delivery Hero SE company. Even better if we could choose to include the issue assignee (if there are any) in the payload or header. That way, the issue ownership rules on Sentry will be the single source of truth to rely on within other triaging platforms we use.

[malor38]

Yes, that is what we want to use it for as well. We can set up the webhook integration with a token for ingestion and per alert, we want to be able to add custom data to each payload. Using a common data model, we can then define how the event should be routed (assigned group name) in each alert, together with attributes like severity. We will have generic correlation searches in the back-end to pick up events from Sentry.

[lobsterkatie]

Make sense. Thanks for the use case examples! I've added this to our backlog, and we'll update here as its status changes. PRs also welcome!

[malor38]

Here is an example of how we are using detectors in Splunk Observability Cloud, where we are embedding custom attributes in each event that is being sent to Splunk: