Age | Commit message (Collapse) | Author | |
---|---|---|---|
2018-02-22 | Updated the file-alerter to use the subject.21-allow-custom-subjects | Steve Kemp | |
If a subject is specified in a test that will now be used for the raise/clear message. This allows testing of the new parser-change(s). | |||
2018-02-22 | If a test has a subject used, then use it. | Steve Kemp | |
2018-02-22 | Removed 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-09-20 | Always ensure we send a trailing \n to graphite. | Steve Kemp | |
This is required for the metrics to be submitted correctly. | |||
2017-09-20 | Update our metric-submission. | Steve Kemp | |
We'll want to handle timeouts more cleanly now, and use TCP. | |||
2017-03-16 | Use the subject-prefix if it is present. | Steve Kemp | |
2016-04-22 | More rubocop fixes. | Steve Kemp | |
2015-12-18 | Removed debugging print. | Steve Kemp | |
2015-11-16 | Keep 8k history-transitions. | Steve Kemp | |
2015-11-16 | Updated the redis-alerter to store more useful-state. | Steve Kemp | |
This will make visualization more simple. | |||
2015-04-16 | Mark unused variables with underscore-prefix. | Steve Kemp | |
This stops warnings when running with "ruby -w". | |||
2015-04-16 | Correctly 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-16 | Resolve 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-09 | Removed trailing whitespace from the code | Steve Kemp | |
2015-03-09 | Remove spaces inside blocks. | Steve Kemp | |
2015-03-09 | Whitespace fixups. | Steve Kemp | |
These were all identified and suggested by rubocop. | |||
2015-03-09 | Removed spaces inside parenthesis. | Steve Kemp | |
2015-03-09 | Prefer single-quotes when you don't need interpolation. | Steve Kemp | |
So "foo" is less good than 'foo'. | |||
2015-03-09 | Do not terminate expressions with ";". | Steve Kemp | |
Ruby is not Perl, much as I sometimes wish it were. | |||
2015-03-09 | Don't use parenthesis aroudn conditions in an if. | Steve Kemp | |
2015-03-09 | Do not use parentheses for method calls with no arguments. | Steve Kemp | |
This is neater. Flagged by rubocop | |||
2015-03-09 | Omit the parentheses in defs when the method doesn't accept any arguments. | Steve Kemp | |
This is neater. | |||
2015-03-09 | Minor indentation fixup. | Steve Kemp | |
2015-03-09 | Avoid arguments we're not using. | Steve Kemp | |
Having methods take arguments which are ignored is a misleading thing, prefix with "_" to make that explicit, or remove. | |||
2015-03-04 | Explictly convert the class to a string. | Steve Kemp | |
This is required under Ruby 1.8, as I discovered when deploying to offsite3. | |||
2015-02-18 | Store the test-class in the redis-state. | Steve Kemp | |
We need to do this such that we can show all possible results of a test in the status-page. There might be three back-ends with different results and if we filter by class-type we'll be able to see that. | |||
2015-02-17 | Deal 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. | |||
2015-02-12 | Make the test-definition available to the redis-alerter. | Steve Kemp | |
2015-02-12 | Updated to require JSON | Steve Kemp | |
2015-02-12 | Updated to store the test results in a set. | Steve Kemp | |
The redis-state "alerter" saves state in a useful way for the future, and will now save an array of hashes - each has corresponding to a useful result. | |||
2015-02-06 | Explicitly report time in MS | Steve Kemp | |
2015-02-05 | Better alerting metric for graphite. | Steve Kemp | |
We now record: custodian.$type.$host.test_duration [time] | |||
2015-02-05 | Don't trash the alert-subject. | Steve Kemp | |
2013-10-08 | Updated to send via UDP, without system. | Steve Kemp | |
2013-10-07 | fixed escaping. | Steve Kemp | |
2013-10-04 | Ensure we quit netcat after sending. | Steve Kemp | |
2013-10-04 | Show the test-target in the graphite list | Steve Kemp | |
2013-10-04 | Graphite alerter. | Steve Kemp | |
2013-07-11 | Read the alert-source for mauve-notifier form the settings object. | Steve Kemp | |
2013-05-15 | Updated comment so they match the functionality of the code. | Steve Kemp | |
2013-04-25 | Correct the body of emails on raise()/clear(). | Steve Kemp | |
Credit to reddit user knothead for spotting this bug. Fixes #4386. | |||
2013-01-24 | fixed | Steve Kemp | |
2013-01-24 | New release | Steve Kemp | |
2013-01-24 | Store the duration of tests. | Steve Kemp | |
2012-12-19 | Ensure that our notification periods are integers | Steve Kemp | |
2012-12-12 | The suppression periods are now configurable too | Steve Kemp | |
2012-12-12 | The suppression period varies between working and out of hours | Steve 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-id | Steve 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. |