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!


Alert count behavior in Opsgenie not clear

serge calderara
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Jun 22, 2021

Dear all,

There is some clarification that I try to get on the way opgenie handle alerts.

What I have unserstand is that the unicity of the Alert is handle through the Alias Field.

In our case we map the Alias field to the ProblemID of Dynatrace integration. With that an alert can be automatically closed when a close state message is received from Opsgenie.

Now what is not clear is how Opgenie will handle the count value ?

As an alert is supposed to be unique from the Alias field, how a new alert can be detected as same as an existing open alert in order that opsgenie increse the count value ?

if a new alert is coming, the alias field will be natively different, does it take in account as well the title ?

Thanks for clarification


1 answer

0 votes
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Jun 24, 2021

Hi @serge calderara 


Alerts de-duplicate based on the alias field as well. so if an alert is created through an integration, and has the same alias field value as an open alert, it will de-duplicate the alert.


As far as what will make it de-duplicate vs close the alert, that depends on if it matches the "Create Alert" action of an integration, or the "Close Alert" action.


If it matches the "Create Alert" action filter, and has the same alias as an open alert, it will de-duplicate. If it does not match the "Create Alert" action filter, but does match the "Close Alert" action filter, then it will close the alert instead of de-duplicating it.


Hope that makes sense.




Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events