Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


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
Community Members
Community Events
Community Groups

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



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?


1 answer

2 votes
Nick H
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
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:




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:



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.

Hi @Nick H ... thank you for this useful post! It helped with exactly the issue I was trying to solve.


Unfortunately, it seems like even though I have updated the alias on both the create and close events in the opsgenie integrations, although it successfully creates alerts on both, when sending a recovery alert from datadog, it is still only closing the alert in one of the opsgenie integrations.


If I remove the one of the responders from datadog, each opsgenie integration works as expected (opening and closing the opsgenie alerts on the messages from datadog), but when both responding integrations are present in datadog, it is creating both alerts in opsgenie, but only closing one on resolution.


Any advice you might have would be helpful, and if you need anything additional from me, like screenshots, please let me know!



Nick H
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Feb 03, 2023

Hi @Jeffrey Tierney ,

I would first check the Logs tab to troubleshoot whether or not Opsgenie is in fact receiving both requests. 

If the request is received, there could be a log that did not match the close action's filter, match on the alias, etc. Those logs might consist of:

Skipping incomingData, no matching actions found

Delaying incomingData, alert with alias does not exist yet

or something along those lines. This would mean there might be a slight misconfiguration in the integration, the alert is already closed, etc.


If the request is not in the logs, then it's most likely a slight misconfiguration on the Datadog or other system's side - since it's not being received by Opsgenie.

@Nick H Thank you for the quick response! 

I might just be missing it, but unfortunately I don't see the logs tab. Where should I look for that... should it be right on the integration detail page within opsgenie? And would I need to have an admin role to see it?

Thanks again!


Nick H
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Feb 03, 2023

Hi @Jeffrey Tierney ,

The Logs tab can be found under the Settings >> Debug section. If you do not see this tab under the Settings, then it's most likely a restriction with your role and permissions. 

By default, only account Admins and Owners have access to the Logs tab. If you have access to this tab - you can search by strings, adjust the timestamp, etc.

@Nick H Thanks again! I will work with one of the opsgenie admins here to get the information.

Like Nick H likes this
Shashwat Khare
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Feb 06, 2023

Hi @Jeffrey Tierney ,
Thanks for letting us know, the Logs should help us understand if the request is being received or not. 

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events