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

Incident not created correctly based on Alert and rules

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.
May 28, 2021

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 :

bsGVJcoF8U.png

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
Atlassian Team members are employees working across the company in a wide variety of roles.
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 https://support.atlassian.com/opsgenie/docs/automatically-create-an-incident-via-incident-rules/

Thanks,

Connor

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events