Unresolved heartbeat alert closed doesn't re-trigger an alert

[David Taylor]

We use Opsgenie heartbeats with the Slack integration. One of our systems went down so a heartbeat failed to reach Opsgenie which resulted in a Slack notification. Our devops operator using Slack closed the alert (prior to the issue being resolved) with the assumption that the heartbeat status would reset and that if the heartbeat still was not received, that a new alert would be generated. A new alert was not generated.

Is this the expected behavior?

Is it possible to configure Opsgenie heartbeats so that closing the alert prematurely would still allow a missing heartbeat to generate a new alert?

[Mubeen Mohammed]

Hello @David Taylor 

Thank you for contacting the Atlassian Community.

Currently, with Opsgenie Heartbeat functionality, an alert is generated when a heartbeat expires. However, if this alert is accidentally closed while the heartbeat remains expired, a new alert will not be created.

We understand the importance of this feature, and our engineering team is aware of it. There is an open feature request for this functionality, and you can view, vote, and comment on it here: https://jira.atlassian.com/browse/OPSGENIE-971.

I hope the details provided are helpful.

Regards

Mubeen Mohammed

Cloud Support Engineer