Skip to content
This repository has been archived by the owner on Dec 8, 2023. It is now read-only.

Pagerduty service can use 'source' as the incident key #22

Open
mheffner opened this issue Jan 3, 2013 · 3 comments
Open

Pagerduty service can use 'source' as the incident key #22

mheffner opened this issue Jan 3, 2013 · 3 comments

Comments

@mheffner
Copy link
Contributor

mheffner commented Jan 3, 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.

@kryptek
Copy link

kryptek commented Jan 7, 2013

Yes..! Exactly what we were looking for! 👍

.. Alfred Moreno is a genius..! 😁

@douglasjarquin
Copy link

@mheffner This would be a great solution for us. 👍

@gclitheroe
Copy link

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
Will allow de duping in PagerDuty using email integration.

A minimal work around for librato#22.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants