A selection of Nagios plugins to monitor services hosted in OpenTable Mesos.
Project description
Basic Nagios/Sensu checks for OpenTable Discovery services.
Distribution
Arguments
Run with -h or --help to see command-line argument documentation.
Interface
If there is an error parsing command-line arguments, we return with exit code 3 (UNKNOWN) and print the invocation error.
If there is an error reaching Discovery and parsing the announcements for your service, we return with exit code 3 (UNKNOWN).
We log critical and warning statuses related to announcement, and return with exit codes 2 (CRITICAL) and 1 (WARNING) respectively.
If your endpoint returns with status code 2xx, this is considered a success. If it returns with 4xx, this is considered a warning (exit code 1). 5xx is considered critical (exit code 2). In the latter two cases, in addition to logging the service status, we log a small number of characters from each endpoint response.
All critical statuses, warnings, and successes are logged, and the exit status of the whole process is the worst of the set.
Endpoint Response Codes
2xx: 0, OK
4xx: 1, WARNING
5xx: 2, CRITICAL
This is a bit of an abuse of HTTP response codes, but our policy is that this is the simplest and most flexible way to get rich status responses from health check endpoints.
Notes
Nagios and Sensu plugin API documentation:
Project details
Release history Release notifications | RSS feed
Download files
Download the file for your platform. If you're not sure which to choose, learn more about installing packages.
Source Distribution
Built Distribution
Hashes for otpl_service_check-1.0.1-py2-none-any.whl
Algorithm | Hash digest | |
---|---|---|
SHA256 | e017751a52924d1b637ac86a268adab6046c379a4249219092098ac034ffc7ca |
|
MD5 | cbc1a8c299a46b3c8871467270da66eb |
|
BLAKE2b-256 | d87b4c1f59465f1a9983e3c215e529ab0b9d6fba9cc328a4609a6c4c9dc67f42 |