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!


What causes an alert to get automatically associated with an incident?

OpsGenie appears to automatically associate ALL alerts with whatever incident happens to be open at the time for the service.  What causes that and how do I turn it off?

Obviously it should be possible to have multiple simultaneous incidents for a single service.

So for instance, if I have a datadog generated alert occur and an incident is created from that alert.  Then if I create an entirely separate alert via Jira integration, OpsGenie will do zero notifications for that alert because it associates it with the incident created by the datadog alert.

That is not great because the second alert is entirely unrelated to the first alert/incident!

1 answer

1 vote
Riley Venable _Atlas Bench_
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Feb 20, 2023
If an alert automatically matches an incident because of an incident rule, after the incident status is resolved, the incident status will be changed from resolved to reopened. Therefore, it is important to close your incidents in a timely manner, because notifications are not sent for alerts matching an open incident.

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events