summaryrefslogtreecommitdiff
path: root/lib/custodian/alerts/mauve.rb
AgeCommit message (Collapse)Author
2015-02-17Deal with multiple test-implementations.Steve Kemp
As soon as we allow multiple test-implementations we get into a mess, as Mauve regards an ID as unique and that is based upon the test-definition not the implementing method We want to allow: * HTTPS test to succeed. * SSL-check to fail. Which means multiple tests of type "https" will have different IDs. Force this by adding on the class of the implementation.
2013-07-11 Read the alert-source for mauve-notifier form the settings object.Steve Kemp
2012-12-19 Ensure that our notification periods are integersrelease-0.8-8Steve Kemp
2012-12-12 The suppression periods are now configurable toorelease-0.8-6Steve Kemp
2012-12-12 The suppression period varies between working and out of hoursSteve Kemp
2012-12-12 Use the SHA1 hash of the input line as the alert ID for mauve.release-0.8-5Steve Kemp
2012-12-10 Use the parser-input as the alert-idSteve Kemp
2012-12-06 We don't set the .detail field unless we're raising an alert.Steve Kemp
This will mean historically we can see what the failure reason was.
2012-11-29 * Added mauve suppression to the mauve alert class.Patrick J Cherry
* Added debian recommendation for mauvealert-client
2012-11-26 Don't attempt to raise/clear with redis/mauve unless they were loaded.Steve Kemp
2012-11-25 Use the user-supplied text, if present.Steve Kemp
2012-11-24 Renamed class to avoid collision.Steve Kemp
2012-11-24 Misc update.Steve Kemp
2012-11-24 Replaced Custodian::Alerter with a full mauve-specific notifier.Steve Kemp
2012-11-24 Initial/stub implementation of a factory for generating alerting objects.Steve Kemp