-
Notifications
You must be signed in to change notification settings - Fork 3
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #113 from Financial-Times/clean-up
Clean up & document
- Loading branch information
Showing
21 changed files
with
346 additions
and
725 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,97 +1,153 @@ | ||
# n-health [![CircleCI](https://circleci.com/gh/Financial-Times/n-health.svg?style=svg)](https://circleci.com/gh/Financial-Times/n-health) | ||
|
||
Makes it easy to add a variety of healthchecks to an app. | ||
Collection of healthcheck classes to use in your nodejs application | ||
|
||
## Adding Health Checks | ||
To Add more health checks create a new file in the `config` directory. It should be a .js file which exports an object. The object must have the following properties: | ||
## Usage | ||
|
||
* name: A name for the healthcheck - is supposed to match to a name in the CMDB, ideally | ||
* description: Test description for the checks - for reference only | ||
* checks: Array of checks - see below for check config | ||
`n-health` exports a function that loads [healthcheck configuration](#healthcheck-configuration) files from a folder: | ||
|
||
## Standard check options | ||
```js | ||
const nHealth = require('n-health'); | ||
|
||
* name, severity, businessImpact, technicalSummary and panicGuide are all required. See the [specification](https://docs.google.com/document/edit?id=1ftlkDj1SUXvKvKJGvoMoF1GnSUInCNPnNGomqTpJaFk) for details | ||
* interval: time between checks in milliseconds or any string compatible with [ms](https://www.npmjs.com/package/ms) [default: 1minute] | ||
* type: The type of check (see below) | ||
* officeHoursOnly: [default: false] For queries that will probably fail out of hours (e.g. Internet Explorer usage, B2B stuff), set this to true and the check will pass on weekends and outside office hours. Use sparingly. | ||
const healthChecks = nHealth( | ||
'path/to/healthchecks' // by default, `/healthchecks` or `/config` in the root of your application | ||
) | ||
``` | ||
|
||
## Healthcheck types and options | ||
It returns an object with an `asArray` method. If you're using `n-express`, pass this array as the `healthChecks` option: | ||
|
||
### pingdom | ||
```js | ||
const nExpress = require('@financial-times/n-express') | ||
|
||
nExpress({ | ||
healthChecks: healthChecks.asArray() | ||
}) | ||
``` | ||
|
||
If you're not using n-express, you should create a `/__health` endpoint which returns the following JSON structure (see the [specification](https://docs.google.com/document/edit?id=1ftlkDj1SUXvKvKJGvoMoF1GnSUInCNPnNGomqTpJaFk) for details): | ||
|
||
```json | ||
{ | ||
"schemaVersion": 1, | ||
"name": "app name", | ||
"systemCode": "biz-ops system code", | ||
"description": "human readable description", | ||
"checks": [] | ||
} | ||
``` | ||
|
||
`checks` should be an array of check status objects. You can get this by calling `getStatus` on each item in the array, for example with `healthChecks.asArray().map(check => check.getStatus())`. | ||
|
||
### Custom healthchecks | ||
|
||
If you require a healthcheck not provided by n-health, you can pass a second argument to `nHealth`, which should be a path to a folder of files exporting custom healthcheck classes. These modules should export a class that extends `n-health`'s `Check` class and implements the `tick` method, which is periodically called to update the check's `status`. It can also implement the `init` to do something when the check is first run. Both of these methods can be `async` if you need to do something like make a request. | ||
|
||
```js | ||
const {Check, status} = require('n-health'); | ||
|
||
class RandomCheck extends Check { | ||
tick() { | ||
this.status = Math.random() < 0.5 ? status.PASSED : status.FAILED; | ||
} | ||
} | ||
|
||
module.exports = RandomCheck; | ||
``` | ||
|
||
See the [src/checks](src/checks) folder for some examples. | ||
|
||
## Healthcheck configuration | ||
|
||
A healthcheck config is a Javascript file that exports an object with these properties. | ||
|
||
* `name`: A name for the healthcheck - is supposed to match to a name in biz-ops, ideally | ||
* `description`: Test description for the checks - for reference only | ||
* `checks`: Array of [check objects](#check-objects) | ||
|
||
### Check objects | ||
|
||
#### Common options | ||
|
||
* `type`: The type of check, which should be one of the types below. That check type's options should also be included in the object as required. | ||
* `name`, `severity`, `businessImpact`, `technicalSummary` and `panicGuide` are all required. See the [specification](https://docs.google.com/document/edit?id=1ftlkDj1SUXvKvKJGvoMoF1GnSUInCNPnNGomqTpJaFk) for details | ||
* `interval`: time between checks in milliseconds or any string compatible with [ms](https://www.npmjs.com/package/ms) [default: 1minute] | ||
* `officeHoursOnly`: [default: `false`] For queries that will probably fail out of hours (e.g. Internet Explorer usage, B2B stuff), set this to true and the check will pass on weekends and outside office hours (defined as 8am-6pm UTC). Use sparingly. | ||
|
||
#### `pingdom` | ||
Will poll the pingdom API to get the status of a specific check | ||
|
||
* checkId: The id of the check in pingdom | ||
* `checkId`: The id of the check in pingdom | ||
|
||
### responseCompare | ||
#### `responseCompare` | ||
Fetches from multiple urls and compares the responses. Useful to check that replication is working | ||
|
||
* urls: An array of urls to call | ||
* comparison: Type of comparison to apply to the responses (Only "equal" so far | ||
* `urls`: An array of urls to call | ||
* `comparison`: Type of comparison to apply to the responses: | ||
- `'equal'` the check succeeds if all the responses have the same status | ||
|
||
### json | ||
#### `json` | ||
Calls a url, gets some json and runs a callback to check its form | ||
|
||
* url: url to call and get the json | ||
* fetchOptions: Object to pass to fetch, see https://www.npmjs.com/package/node-fetch#options for more information. | ||
* callback: A function to run on the response. Accepts the parsed json as an argument and should return true or false | ||
* `url`: url to call and get the json | ||
* `fetchOptions`: Object to pass to fetch, see https://www.npmjs.com/package/node-fetch#options for more information. | ||
* `callback`: A function to run on the response. Accepts the parsed json as an argument and should return true or false | ||
|
||
### aggregate | ||
Reports on the status of other checks. Useful if you have a multi-region service and, if one check fails it is not as bad as if ALL the checks fail. | ||
#### `aggregate` | ||
Reports on the status of other checks. Useful if you have a multi-region service and, if one check fails it is not as bad as if ALL the checks fail. | ||
|
||
* watch: Array of names of checks to aggregate | ||
* mode: Aggregate mode. I think "atLeastOne" is the only valid option so far | ||
* `watch`: Array of names of checks to aggregate | ||
* `mode`: Aggregate mode: | ||
- `'atLeastOne'` the check succeeds if at least one of its subchecks succeeds | ||
|
||
### graphiteSpike | ||
#### `graphiteSpike` | ||
Compares current and historical graphite metrics to see if there is a spike | ||
|
||
* numerator: [required] Name of main graphite metric to count (may contain wildcards) | ||
* divisor: [optional] Name of graphite metric to divide by (may contain wildcards) | ||
* normalize: [optional] Boolean indicating whether to normalize to adjust for difference in size between sample and baseline timescales. Default is `true` if no divisor specified, `false` otherwise. | ||
* samplePeriod: [default: '10min'] Length of time to count metrics for a sample of current behaviour | ||
* baselinePeriod: [default: '7d'] Length of time to count metrics for to establish baseline behaviour | ||
* direction: [default: 'up'] Direction in which to look for spikes; 'up' = sharp increase in activity, 'down' = sharp decrease in activity | ||
* threshold: [default: 3] Amount of difference between current and baseline activity which registers as a spike e.g. 5 means current activity must be 5 times greater/less than the baseline activity | ||
* `numerator`: [required] Name of main graphite metric to count (may contain wildcards) | ||
* `divisor`: [optional] Name of graphite metric to divide by (may contain wildcards) | ||
* `normalize`: [optional] Boolean indicating whether to normalize to adjust for difference in size between sample and baseline timescales. Default is `true` if no divisor specified, `false` otherwise. | ||
* `samplePeriod`: [default: `'10min'`] Length of time to count metrics for a sample of current behaviour | ||
* `baselinePeriod`: [default: `'7d'`] Length of time to count metrics for to establish baseline behaviour | ||
* `direction`: [default: `'up'`] Direction in which to look for spikes; 'up' = sharp increase in activity, 'down' = sharp decrease in activity | ||
* `threshold`: [default: `3`] Amount of difference between current and baseline activity which registers as a spike e.g. 5 means current activity must be 5 times greater/less than the baseline activity | ||
|
||
### graphiteThreshold | ||
#### `graphiteThreshold` | ||
Checks whether the value of a graphite metric has crossed a threshold | ||
|
||
* metric: [required] Name of graphite metric to count (may contain wildcards) | ||
* threshold: [required] Value to check the metrics against | ||
* samplePeriod: [default: '10min'] Length of time to count metrics for a sample of current behaviour | ||
* direction: [default: 'above'] Direction on which to trigger the healthcheck; | ||
- 'above' = alert if value goes above the threshold | ||
- 'below' = alert if value goes below the threshold | ||
* `metric`: [required] Name of graphite metric to count (may contain wildcards) | ||
* `threshold`: [required] Value to check the metrics against | ||
* `samplePeriod`: [default: `'10min'`] Length of time to count metrics for a sample of current behaviour | ||
* `direction`: [default: `'above'`] Direction on which to trigger the healthcheck: | ||
- `'above'` = alert if value goes above the threshold | ||
- `'below'` = alert if value goes below the threshold | ||
|
||
### graphiteWorking | ||
#### `graphiteWorking` | ||
|
||
Checks if the value of a graphite metric has received data recently. | ||
|
||
* metric: [required] Name of graphite metric to count (may contain wildcards) | ||
* `metric`: [required] Name of graphite metric to count (may contain wildcards) | ||
- Use `summarize` if the metric receives data infrequently, e.g. `summarize(next.heroku.next-article.some-infrequent-periodic-metric, '30mins', 'sum', true)` | ||
* time: [default: '-5minutes'] Length of time to count metrics | ||
* `time`: [default: `'-5minutes'`] Length of time to count metrics | ||
|
||
### cloudWatchThreshold | ||
#### `cloudWatchThreshold` | ||
Checks whether the value of a CloudWatch metric has crossed a threshold | ||
|
||
_Note: this assumes that `AWS_ACCESS_KEY` & `AWS_SECRET_ACCESS_KEY` are implictly available as environment variables on process.env_ | ||
|
||
|
||
* cloudWatchRegion = [default 'eu-west-1'] AWS region the metrics are stored | ||
* cloudWatchMetricName = [required] Name of the CloudWatch metric to count | ||
* cloudWatchNamespace = [required] Namespace the metric resides in | ||
* cloudWatchStatistic = [default 'Sum'] Data aggregation type to return | ||
* cloudWatchDimensions = Optional array of metric data to query | ||
* samplePeriod: [default: 300] Length of time in seconds to count metrics for a sample of current behaviour | ||
* threshold: [required] Value to check the metrics against | ||
* direction: [default: 'above'] Direction on which to trigger the healthcheck; | ||
- 'above' = alert if value goes above the threshold | ||
- 'below' = alert if value goes below the threshold | ||
|
||
### cloudWatchAlarm | ||
* `cloudWatchRegion` = [default `'eu-west-1'`] AWS region the metrics are stored | ||
* `cloudWatchMetricName` = [required] Name of the CloudWatch metric to count | ||
* `cloudWatchNamespace` = [required] Namespace the metric resides in | ||
* `cloudWatchStatistic` = [default `'Sum'`] Data aggregation type to return | ||
* `cloudWatchDimensions` = Optional array of metric data to query | ||
* `samplePeriod`: [default: `300`] Length of time in seconds to count metrics for a sample of current behaviour | ||
* `threshold`: [required] Value to check the metrics against | ||
* `direction`: [default: `'above'`] Direction on which to trigger the healthcheck: | ||
- `'above'` = alert if value goes above the threshold | ||
- `'below'` = alert if value goes below the threshold | ||
|
||
#### `cloudWatchAlarm` | ||
Checks whether the state of a CloudWatch alarm is health | ||
|
||
_Note: this assumes that `AWS_ACCESS_KEY` & `AWS_SECRET_ACCESS_KEY` are implictly available as environment variables on process.env_ | ||
|
||
* cloudWatchRegion = [default 'eu-west-1'] AWS region the metrics are stored | ||
* cloudWatchAlarmName = [required] Name of the CloudWatch alarm to check | ||
* `cloudWatchRegion` = [default `'eu-west-1'`] AWS region the metrics are stored | ||
* `cloudWatchAlarmName` = [required] Name of the CloudWatch alarm to check |
This file was deleted.
Oops, something went wrong.
This file was deleted.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.