This project has been archived by its maintainers, and is no longer receiving any updates.
A Nagios plugin that collects response times from logs.
Usage: check_responsetime --logfile /path/to/logfile
The plugin remembers the timestamp of the latest log entry it has seen on each run, and on the next run only considers log entries that are more recent.
Log format
The supported log format is as follows:
<timestamp> "<http-verb> <path> <http-version>" <responsetime>
timestamp: %d/%b/%Y:%H:%M:%S %z
http-verb: GET, POST
path: the requested URL path
http-version: e.g. HTTP/1.1
responsetime in seconds, e. g. 0.5
Example:
17/May/2011:14:11:18 +0200 "GET /index.html HTTP/1.1" 0.289
An example configuration for the nginx server looks like this:
http {
log_format timing '$time_local "$request" $upstream_response_time';
server {
access_log /path/to/timing.log timing;
}
}
Future directions
One obvious additional feature is the ability to define thresholds (e.g. “a mean responsetime above 3 seconds is WARN, above 5 CRITICAL”)
Development
The source code is available in the mercurial repository at https://code.gocept.com/hg/public/nagios.responsetime
Please report any bugs you find to Wolfgang Schnerring.
Changes
1.0.4 (2012-12-07)
Explicitly declare our dependency on nagiosplugin < 0.5
Fix API incompatibility in test suite.
1.0.3 (2011-12-08)
If no records are availble for this check period, return empty performance values (all zero) to avoid UNKNOWN state that is only noise.
1.0.2 (2011-11-14)
Fixed divide by zero bug when there is only a single entry (#9332).
1.0.1 (2011-09-04)
Fixed bug when there are no log entries for the current interval (#9332).
1.0 (2011-07-01)
Fixed bug with incomplete log file lines (“invalid literal for float(): -“).
1.0rc1 (2011-06-10)
First release.
Metadata
Release files for nagios.responsetime 1.0.4
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| nagios.responsetime-1.0.4.tar.gz | 8.0 kB | Without provenance | Details for nagios.responsetime-1.0.4.tar.gz |
Release files / nagios.responsetime-1.0.4.tar.gz
| Download URL | nagios.responsetime-1.0.4.tar.gz |
|---|---|
| Size | 8.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f526d5b4b32d69b0e70bd20d08bebd23fe3883c847221bb43ccb0606458a2d3e
|
|
BLAKE2b-256 checksum How to use checksums |
278cafe6abe335dc3b7b45d84339bf72ea8ebadc63e0edc1c2670512458fbe10
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for nagios.responsetime 1.0.4
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.