Refactor, redocument, refresh

• graphite healthchecks are no longer next-specific
• removed memory check that hasn't been usable since 2016
• improve documentation and fully explain how to use in an app (n-express or vanilla)
• refactor to use async/await

Remove keen healthchecks

All the usages have been removed, so this is no longer breaking.

Updates 'graphiteWorkingCheck' to look at timestamp

This release alters the behaviour of graphiteWorkingCheck to look at timestamps rather than just the number of datapoint since the last non-null value.

WARNING: This will expose broken metrics that would otherwise show false positives, such as metrics using the summarise() function.

Upgrade to the new Graphite system

Merge pull request #101 from Financial-Times/graphite-migration

Point Graphite checks at the new system

Fix nulls test in graphiteThreshold

Now nulls are ignored in graphiteThreshold – use graphiteWorking for that.

Adding graphiteSumThreshold

This check sums all the values in the results and runs against a defined threshold

Adding back fromTime override in graphiteWorking check

Merge pull request #94 from Financial-Times/lk/graphite-working-time

Adding back override to graphiteWorking

graphiteThreshold to ignore nulls in metric data in favour of using graphiteWorking

get graphiteThreshold to ignore nulls (#93)

add comments to encourage the use of graphiteWorking for nulls

refactor graphiteWorking to better deal with wildcarded metrics and to
fail when the last three consecutive datapoints are nulls

 🐿 v2.9.0

tell us which specific targets (metrics) fail for wildcarded targets

v2.3.4

tell us which specific targets (metrics) fail for wildcarded targets …

v2.3.3: Merge pull request #90 from Financial-Times/fix-below-threshold-check

Parse null responses from graphite