summaryrefslogtreecommitdiff
path: root/lib/custodian/alerts/mauve.rb
AgeCommit message (Collapse)Author
2018-02-22If a test has a subject used, then use it.Steve Kemp
2018-02-22Removed obsolete code.Steve Kemp
The intention of this series of changes is to allow subjects to be replaced for specific tests. The idea of replacement replaced the idea of a custom-prefix - so I've removed that code before proceeding.
2017-03-16Use the subject-prefix if it is present.Steve Kemp
2016-04-22More rubocop fixes.Steve Kemp
2015-04-16Mark unused variables with underscore-prefix.Steve Kemp
This stops warnings when running with "ruby -w".
2015-04-16Correctly use the result of the resolution in the alert.Steve Kemp
There was a bug in that we used the same local-variable "result" for two purposes, trashing the intended use-case.
2015-04-16Resolve hostnames for both A + AAAA.Steve Kemp
The Bytemark-specific notifier, using mauve, appends some text to the bottom of each alert: http://example.com/ resolves to 1.2.3.4 which is INSIDE|OUTSIDE bytemark This text was previously limited to the IPv4 address, but now is repeated for each family which resolves successfully. This closes #10568. This fixes #10568.
2015-03-09Removed trailing whitespace from the codeSteve Kemp
2015-03-09Whitespace fixups.Steve Kemp
These were all identified and suggested by rubocop.
2015-03-09Removed spaces inside parenthesis.Steve Kemp
2015-03-09Prefer single-quotes when you don't need interpolation.Steve Kemp
So "foo" is less good than 'foo'.
2015-03-09Don't use parenthesis aroudn conditions in an if.Steve Kemp
2015-03-09Do not use parentheses for method calls with no arguments.Steve Kemp
This is neater. Flagged by rubocop
2015-03-09Omit the parentheses in defs when the method doesn't accept any arguments.Steve Kemp
This is neater.
2015-03-04Explictly convert the class to a string.Steve Kemp
This is required under Ruby 1.8, as I discovered when deploying to offsite3.
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 integersSteve Kemp
2012-12-12 The suppression periods are now configurable tooSteve 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.Steve 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