You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Dec 8, 2023. It is now read-only.
In a scenario where you have many metrics across a set of common sources, an incident or outage on a single source can cause multiple metrics to simultaneously cross their configured alert thresholds. This can lead to an Pagerduty alert storm for a single incident on a single source. It would be preferable to collapse multiple Pagerduty alerts from the same source.
To support this we would need to have the option to use the source name as the Pagerduty incident_key. Simplest solution would be to have a boolean option that denoted "use source as incident key". That should address this use case.