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

Incident not created correctly based on Alert and rules

Dear all,

We have different Alert which are occuring in Opgenie from dynatrace.
Then we define an Incident rule which create an Incident if Alert priority is P3

What we noticed is that when we have different Alert with priority P3, only 1 single incident is created event if the Alert is not the same as seen below :


Associated Alert to the above incident

Any idea why I have only 1 incident with all alert in?

1 answer

0 votes
Connor Eyles Atlassian Team May 30, 2021

Hi @serge calderara 

I hope you are doing well smile

So when it comes to automating Incidents via Incident rules, we have something called Auto-matched Alert Behavior. After an incident is opened, alerts matching the Incident Rules become Associated Alerts under the incident automatically, and no notification is sent. This aims to reduce alert fatigue.

So what you will need to do is check all the associated alerts and see if they all match the Incident rule. 

You can find more information here



Suggest an answer

Log in or Sign up to answer

Atlassian Community Events