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

Auto-close an incident when no related alerts are active

Dear all,

I was wondering if there is an automatic method to close an incident when all of its alerts are closed, currently I am doing this "by hand" meaning that through the API, when an alert is being closed, I check whether or not the incident has active alerts and if it has not, I close the incident as well as the alert.
I noticed that it this way, sometimes, for example when I close 2 alerts consequently, due to the asynchronous nature of the Opsgenie API, the result of the count API call is not always consistent and I had to set a delay of 2 seconds to make it worked properly.

Is there someone that has already faced this problem and came up with a more elegant solution?

Thanks in advance,

1 answer

1 accepted

1 vote
Answer accepted
Justin Sitarz
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Aug 24, 2021

Hi Alessandro, 


Justin here, from Opsgenie support - happy to help!


Unfortunately, I think the way you're doing this currently is probably one of the better options, as there is not a way to automatically close incidents out when all of the responder alerts are closed (though we do have a feature request for that - request id AG-347, for reference). And, as you mentioned, due to the asynchronous processing of requests, there may be a second or two delay between the close alert request being made and the actual alert being closed out - necessitating a small delay on your end when checking if the count of open responder alerts for your incident is zero.


The hope would be that we enable some built in functionality to address this use case - so what I can recommend is checking in with Opsgenie support (either through the in-app chat or through the Atlassian support portal) on the status of the request periodically, referencing the ID above.


Hopefully that helps to answer your question, but please do let me know if you have any others, or if there's anything else we can assist with. Thanks!


Justin S.

Opsgenie Support

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events