Can I alert multiple team integrations from a single Datadog alert?
Asked by Greg Scott:

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](/t5/user/viewprofilepage/user-id/1671990)-Incident_Sheriff [@OpsGenie](/t5/user/viewprofilepage/user-id/1671990)-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!


Answers:
author: Nick H
body: Hi [@Greg Scott](/t5/user/viewprofilepage/user-id/5038568) ,

That is possible - but what typically happens with this use case and Datadog specifically is the alert [deduplicates](https://support.atlassian.com/opsgenie/docs/what-is-alert-de-duplication/).

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](https://community.atlassian.com/t5/image/serverpage/image-id/217764iB55672C5B600443B/image-size/large?v=v2&px=999 "dd1.jpg")

![dd2.jpg](https://community.atlassian.com/t5/image/serverpage/image-id/217765i7D6F3526FDF09BF8/image-size/large?v=v2&px=999 "dd2.jpg")![dd3.jpg](https://community.atlassian.com/t5/image/serverpage/image-id/217766iE9F431B69FD8497E/image-size/large?v=v2&px=999 "dd3.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](https://community.atlassian.com/t5/image/serverpage/image-id/217767i74F0653941F53934/image-size/large?v=v2&px=999 "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.

comments: author: Jeffrey Tierney
body: Hi [@Nick H](/t5/user/viewprofilepage/user-id/2540930) ... 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!

Thanks!


author: Nick H
body: Hi [@Jeffrey Tierney](/t5/user/viewprofilepage/user-id/5138344) ,

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.


author: Jeffrey Tierney
body: [@Nick H](/t5/user/viewprofilepage/user-id/2540930) 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!

Jeff


author: Nick H
body: Hi [@Jeffrey Tierney](/t5/user/viewprofilepage/user-id/5138344) ,

The [Logs tab](https://support.atlassian.com/opsgenie/docs/search-logs/) 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](https://support.atlassian.com/opsgenie/docs/learn-user-roles-and-permissions/) 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.


author: Jeffrey Tierney
body: [@Nick H](/t5/user/viewprofilepage/user-id/2540930) Thanks again! I will work with one of the opsgenie admins here to get the information.


author: Shashwat Khare
body: Hi [@Jeffrey Tierney](/t5/user/viewprofilepage/user-id/5138344) ,  
Thanks for letting us know, the Logs should help us understand if the request is being received or not.


author: Oleksandr Shmyrko
body: We have the same issue. We can create multiple Opsgenie alerts using one Datadog monitor that has multiple team integrations specified, but only one Opsgenie alert is closed when the monitor sends recovery alerts (seems it sends only one recovery alert).

Datadog support confirmed that the issue is on their side:
> I have confirmation from the escalation team that the Opsgenie integration does not currently support utilizing multiple notification (@ handles) in 1 monitor. That is why the additional 2 are not coming through.

They suggested opening a feature request to support such behavior in Opsgenie integration, however this looks more like a bug.

comments: author: Shashwat Khare
body: Hello [@Oleksandr Shmyrko](/t5/user/viewprofilepage/user-id/5311714) ,  

Thanks for bringing this to our attention.  

May I please ask you to log an email ticket with us so that we can investigate if there's an alias mapping configured on your Datadog integration and further understand why the recovery alarm from Datadog is not closing the expected opsgenie alert.  

Please use [this link](https://support.atlassian.com/contact/#/?inquiry_category=technical_issues&impact=4&is_cloud=true&product_key=opsgenie&customer_working_hours=0800-1700&support_type=customer) to log an email ticket with us mentioning the integration name as well as one sample alert that should be auto-closed via the Datadog integration:  

Best,  
Shashwat


Tags: cloud

datadog