graphite-beacon
graphite-beacon copied to clipboard
klen
Simple alerting system for Graphite metrics
I'd like to set a different to: address for a specific alert. How can I do that?
It would be nice to customize a notification message for each handler. For example, in Slack you may want to make an [announcement](https://get.slack.help/hc/en-us/articles/202009646-Making-announcements) alerting the entire "@channel" or just online...
This fixes the issue #86 The changes are backward compatible.
When some HTTP requests take too long, the queue of requests gets filled up and other requests, that shouldn't fail, fail too with timeouts / too long to process errors....
I am using graphite-beacon to monitor a production service that sees varying load patterns throughout the day and by day of week. I've added the ability to use cron syntax...
The code will use the yaml loader only if the extension is .yml (see https://github.com/klen/graphite-beacon/blob/develop/graphite_beacon/core.py#L98)
Add a method of comparison like historical. It's more suitable for something periodic, only used in graphite. I think it's useful in actual work.
PagerDuty incidents are generated with messages like: ``` [BEACON] CRITICAL (stats.gauges.server2.data) failed. Current value: 1.0 ``` "Back to normal" messages look like: ``` [BEACON] NORMAL (stats.gauges.server1.data) is back to normal....
It appears that repeat_interval works only as a global setting. It would be useful to set this per alert as part of the alert definition.
Gives more freedom to alerts to specify warning, critical, and normal handlers as well as To and From for smtp as well as commands for cli.
