Delaying incident creation

[Nicki]

We are trying to use OpsGenie to manage alerts in our command centre, but I'm having issues with the automatic incident creation.

Ideal solution:

• alert comes in
• more alerts for the same issue arrive, and causes the count to increase
• no notification takes place unless the de-duplication threshold is passed
• If the threshold is not passed and no new alerts within the auto-close time, the alert is closed without notification and without incident being created.
• if the de-dup threshold is passed, notification and incident rules are fired causing teams to be notified and incident to be created.

This will enable the team to manage incidents and not get overwhelmed by alerts, and ensure consistent incident creation. It will also avoid unnecessary incident creation for an alert that closes before notification takes place.

I found an open issue for this, please go and upvote it: https://jira.atlassian.com/browse/OPSGENIE-1059

[Rafael Meira]

Hey Nicki, thank you for all your explanation and also to put yourself already for the Feature Request.

Unfortunately, we don't have these features adjusted as you currently want, which is why we the feature request was indeed opened.

Once we have more information/updates you will receive a notification as you are already in this Feature request.

https://jira.atlassian.com/browse/OPSGENIE-1059

Best of luck,
Rafa

[Nicki]

Thank you.