Avoid duplicate alerts

[Prakash Gula]

Hi,

I have configured integration from Grafana to send alerts to opsgenie. The alert needs to be sent only once even though issue still exists in Grafana. If the issue still exists in Grafana then alert is sent again till the issue is resolved that means changes to the latest data in Grafana from source. Anyone done team config changes in opsgenie to alert once based on the source match and forgot, avoiding multiple alerts is what I am looking. I did read about deduplication but that didn't provide more insights of what I am looking for. Thanks

[John M]

Hi @Prakash Gula ,

Deduplication is designed to address the exact use-case you've outlined. You would need to select a dynamic field used to deduplicate the alerts and insert that into the 'alias' field in the integration's advanced setting. Here is an article on configuring the alias that you may find helpful:

https://community.atlassian.com/t5/Opsgenie-articles/Configuring-the-Opsgenie-Alias-Field/ba-p/2520231

[Thibault Ajon]

How can we stop alert de-duplication ? 

I have an alert on like 7 metrics and i want to receive an alert every time 1 metric trigger. 
I wont receive notification if the count increase because another metric trigger even if it's a new alerts. 

When i have to treat dozens and dozens alerts i dont have time to check if the count increase or not.

[John M]

@Thibault Ajon You cannot stop alert deduplication. You would need to update your alias so that the alerts are not deduplicating. The alias should be unique if you want to receive notifications. You can use dynamic fields along with regex and string processing to generate unique aliases:

https://support.atlassian.com/opsgenie/docs/string-processing-methods-in-opsgenie-integrations/

https://support.atlassian.com/opsgenie/docs/regular-expressions-for-improved-alert-filtering/

[Thibault Ajon]

Hello, thx for your reply, 
isn't {{alias}} already a dynamic field ?