Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,364,887
Community Members
 
Community Events
168
Community Groups

Can I alert multiple team integrations from a single Datadog alert?

Edited

Hello,

I'd like certain alerts created in datadog to page multiple teams at the same time (and add them both as responders). I have a separate datadog integration for each team, and I've tried adding multiple mentions in the datadog alert (e.g. @OpsGenie-Incident_Sheriff @OpsGenie-CTW_Team). When the alert fires, only one of the teams is added as a responder (seemingly at random). Anything I can change the remedy this?

Thanks!

1 answer

1 vote
Nick H Atlassian Team Sep 26, 2022

Hi @Greg Scott ,

That is possible - but what typically happens with this use case and Datadog specifically is the alert deduplicates.

Deduplication occurs when the alias of an alert matches the alias of an open existing alert. In this case, it's happening almost immediately at alert creation for all these - and it's important to note that it can occur across multiple integrations. Again, only the alias needs to match.

You can edit what data parses in the alias field under the integration's Advanced tab. We see most customers adding a string of hardcoded data such as the integration's name to differentiate the alias for each alert:

dd1.jpg

dd2.jpgdd3.jpg

 

Note as well that if you edit what parses in the alias field of the Create Alert action, you'll want to consider editing this in all other integration actions so Opsgenie can identify which alert to also close, ack, etc. through the integrations. Whatever parses in the alias field should be consistent throughout the integration:

dd4.jpg

 

Lastly, the Advanced tab is only available on the Opsgenie Standard and Enterprise plans (and JSM-OG Premium and Enterprise plans). If you do not see this tab, then you plan does not have this functionality - and unfortunately there isn't a workaround.

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
TAGS

Atlassian Community Events