Migration to internal Graphite

You may get an error when you attempt to start up the app, saying that a Graphite health check metric query needs to have next. prepended to it. Please fix the query to have the next. prepended. You will need to do this for all queries. Then the app should start up OK. If there are issues with health checks, please contact @bjfletcher, @wheresrhys or @commuterjoy

Remove: minSeries + maxSeries in threshold check

Using minSeries or maxSeries causes problems in Graphite (and subsequently failing health checks) if the list is empty.

It now iterates over all sets of results that the query returns, and employs use of some() method, so immediately returning true at first instance of a datapoint that breaches a given threshold, and so improving performance.

v1.11.0: Merge pull request #38 from Financial-Times/rhys/prevent-api-misuse

prevent overriding of important error handling behaviour

Remove graphiteThreshold logging

v1.10.4

Don't log graphiteThreshold result

Handle empty series for graphiteThreshold

Also change it to actual series values, rather than taking an average

Fix bug with cloudWatchMetricName config

Fixes a bug in the cloudWatchThreshold check which had a typo in the configuration.

Export cloudWatch checks

ronseal

CloudWatch checks

Adds two new check types to monitor AWS ClousWatch based metrics and alarms:

• cloudWatchThreshold
• cloudWatchAlarm

v1.9.0: Merge pull request #28 from Financial-Times/rhys/graphite-limit

added health check type to check metric doesn't exceed a value

Return from _tick method

v1.8.2

Return from _tick