I have a notification policy that applies to all alerts where notifications are delayed unless the alert occurs 10 time within 11 minutes and also has an Auto Close policy for 10 minutes after the last occurence.
The problem is that, if an alert is not resolved and reaches a deduplication count of 100 (the maximum before the count stops going up), the auto close policy kicks in and closes the original alert and a new alert gets created, thus restarting the notification policy and resending notifications about every 2 hours.
Is there a way to fix this or get around it? Preferably, the auto close policy would not activate even if the deduplication count is 100 seeing OpsGenie is in fact still receiving alerts, just not increasing the deduplication count.
Right now, this functionality can't be changed. However, we do have a feature request to keep counting the alerts past 100 for the auto-close policies. The ticket number for this is ALX-3024. We don't have an external-facing Jira to track these, but you can reach out to us and reference that number if you're looking for an update in the future.
Back in April of last year one of the major product announcements from Opsgenie was the launch of the Incident investigation view which created a deep connection between Bitbucket and Opsgenie, empow...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event