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

Opsgenie do not send heartbeat alert if incident of another service

Daniel Albion August 30, 2022

Opsgenie should not send an heartbeat alert if there is an incident by another service. Is this possible to prevent?

1 answer

0 votes
Shivam Naik
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
September 1, 2022

Hi @Daniel Albion ,

Happy to help!

When you set up Heartbeats using the email seen in the integration:

An alert will be generated when the Heartbeat is detected to be expired on the Service being monitored with that email. When you say prevent an alert from another Service, are you wanting to prevent Heartbeat alerts from being created from a specific monitored Service, did you mean you wanted to disable those Alerts for that Service, or do you mean you want to be able to filter on Heartbeat alerts to create Alerts for specific Heartbeat responses?

At the moment, there isn't a way to filter for specific responses on Heartbeats, the Alert will get created as soon as Expiration is detected, but if that is what you were looking for, we can get a Feature Request filed to add it to the Heartbeat function in future releases.

Please let me know if I've understood your request correctly, and I will follow up accordingly

Daniel Albion September 5, 2022

Hey @Shivam Naik

no, this does not really solve my problem. I want the heartbeat to depend on a service of another team. When team B's heartbeat HB_B expires, it should be checked whether team A's service ServiceA has an incident. If this is the case, then HB_B should not alert. Is it possible to check this and create a condition like this?

Shivam Naik
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
September 8, 2022

Hi @Daniel Albion ,

I ran the scenario you mentioned by my team, and what you could do is set up an Incident Rule on Team A that matches for the Heartbeat alert being created, with Service A (owned by Team A) attached, so the rule itself would look something like this. You could even set it as Match Any conditions, so that it triggers for different types of alerts :

This will generate an Incident when triggered. Any subsequent alerts matching this policy would then be made Associated Alerts, and not notify based on its association with an ongoing incident on Team A until it is closed


Please let me know if you have any follow up questions

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events