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 has been 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.
The text was updated successfully, but these errors were encountered:
Plus one on this. It would be ideal to use the metric_name and source as the incident key. I think particularly with Librato set up for dynamic instruments and dashboards this is the bare minimum functionality for alerting.
gclitheroe
pushed a commit
to gclitheroe/librato-services
that referenced
this issue
Jul 5, 2013
This is the use case:
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.
The text was updated successfully, but these errors were encountered: