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

Alert de-duplication in OpsGenie when processing DataDog events


After reading the support doc. I am trying to find a way to avoid duplication on alerts created from DataDog Monitor events.

I have been trying to modify the "alias" field mentioned here from DataDog end with zero luck.


Some documentation about this or a working example would be really appreciated.

1 answer

1 accepted

1 vote
Answer accepted

Hi @Daniel Prado Martinez ,

Sometimes we'll the issue of Datadog alerts being deduplicated through multiple Datadog integrations. Is this the case with you? Or is this only for one integration?

If the deduplication is due to multiple integrations, an easy fix is adding some hardcoded data into the alias field of all the integration actions. Typically we'll see customers simply adding the name of the integration along with {{alias}} like so:



This will help differentiate the alerts a bit to avoid deduplication from multiple integrations, but also allow for the same integration to close, ack, etc. the alert.

Hope that helps!

This is not exactly what I was looking for, but serves the purpose perfectly.


Suggest an answer

Log in or Sign up to answer

Atlassian Community Events