Allow Configuring OpsGenie Teams for Alert Rules

[kerenkhatiwada]

Problem Statement

The current OpsGenie integration is a Legacy integration. Currently, it is not possible to configure alert rules to send alerts to different OpsGenie teams for the same Sentry Project. The request is to have Sentry improve the OpsGenie integration to allow for configuring alert rules to send alerts to different OpsGenie teams for the same Sentry project.

Solution Brainstorm

No response

┆Issue is synchronized with this Jira Improvement by Unito

[getsantry]

Assigning to @getsentry/support for routing, due by Monday, March 20th at 14:02 (yyz). ⏲️

[getsantry]

Routing to @getsentry/ecosystem for triage, due by Tuesday, March 21st at 11:03 am (sfo). ⏲️

[cansin]

@brianthi will this be eventually worked on? Or should we assume that given OpsGenie is a legacy integration this feature might never arrive? I am trying to see if we should spend time creating a custom integration for our organization for this exact same purpose. Thank you for your time 🙏

[Dhrumil-Sentry]

Hi @cansin thanks for bringing up this issue. a couple of questions:

1. Is it not possible for you to route the alert to the right team within Opsgenie itself?
2. Is there something missing in the Sentry payload that prevents you from doing this?

We don't have any concrete plans to work on Opsgenie at this moment and that will likely be true for the next couple of quarters at least.

[Lingviston]

I can add more details on this. Hope it'll lead to the issue re-opening.

Opsgenie gives a bit limited capabilities in terms of team-to-team routing:

• You can't route to another team or escalation of another team from the "team routing rule";
• It looks like you can route to another team only from the escalation, which is too high level;
• Though you can route to another team from an escalation - you still can't route to an escalation of that team;
• All of the escalation/routing rules mentioned above have to be linked to the original team linked with Sentry. It means that analytics, which is automatically calculated by the OpsGenier, will be at least partially if not fully calculated for the original team instead of the routed one;
• Finally, it just makes the configuration way more complex as the "target team" have to modify the "original team's" config for way too many reasons.

[Dhrumil-Sentry]

Thanks for the feedback @Lingviston - This is currently on our backlog and we'll hopefully have an update about this soon.

If Sentry allowed you to choose an Opsgenie Integration and the Opsgenie team/service in your Sentry alert rules would that work for you?

That's how our Pagerduty integration works today: