Add ability to customize alert behavior with no data #43
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Includes readme updates
|
Very handy as we put instances down as part of scaling process. |
klen
added a commit
that referenced
this pull request
Jun 25, 2015
Add ability to customize alert behavior with no data
|
Thank you for the pull request! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
New 'no_data' config value can now be set to 'normal', 'warning' or 'critical' at the top-level, or per alert. Default retains the same behavior as today: 'critical' alerts. Includes associated readme updates.
Background
I'm using statsd to keep track of a few metrics like 'crashes', 'deploys' and 'launches.' Whenever these are non-zero, I want a notification. As you might expect, I only send data from my scripts and apps when it's non-zero. Statsd takes care of this for me, by remembering the data point after I initially send it, sending zeros thereafter (this is configurable, of course).
When I need to restart statsd or the entire machine, those data points are no longer known to statsd. Today I get critical alerts whenever this happens. This allows that logging level for 'no data' to be configured both globally and per-alert.