Home Directory Plugins Web Servers Apache check_apachestatus_auto (with lighttpd support)

Search Exchange

Search All Sites

Nagios Live Webinars

Let our experts show you how Nagios can help your organization.

Contact Us

Phone: 1-888-NAGIOS-1
Email: sales@nagios.com

Login

Remember Me

check_apachestatus_auto (with lighttpd support)

Rating
2 votes
Favoured:
0
Network Monitoring Software - Download Nagios XI
Log Management Software - Nagios Log Server - Download
Netflow Analysis Software - Nagios Network Analyzer - Download
A Nagios plugin that parses the status page of an apache or lighttpd server and returns the amount of idle, busy, open and total slots, as well as Requests/sec, Bytes/Request and Bytes/sec. Usable with user authentication and non standard apache server-status urls. This is an enhanced version of an enhanced version of Lieven De Bodt’s check_apachestatus.pl.
A Nagios plugin that parses the status page of an apache or lighttpd server, the plugin returns the response time, the amount of idle, busy, open and total slots. The perfdata returns the status of all slots including Requests/sec, Bytes/Request and Bytes/sec. Optionally you can specify how much slots should be available. Use http(s) and basic user authentication with non standard server-status urls. This is an enhanced version of an enhanced version of Lieven De Bodt’s check_apachestatus.pl.

Why an extra plugin?
First it uses the ?auto parameter instead of parsing the human readable status output - this reduces possible parsing errors. Then it uses a different syntax of the url parameter. And notably most of all it recalculates the Request/sec and the other values by itself instead of using the given apache server-status values.

Why recalculating the Request/sec vaules?
Visit check_apachestatus_auto homepage

Whats new
v1.3 2020-05-29 Fixed non numeric uptime (Andre Hotzler)
Reviews (1)
bywt47a, January 26, 2016
It is an perfect plugin it produces a lot of statistic it is flexible and it works.

.. But I've found minor bug related to plugin execution tests.
In some case it can result in message "Not output from plugin" bla bla bla.
Steps to reproduce:
1. Invoke test check from CCM (In fact, it runs as root on system level)
2. Wait for regular execution during nagios hosts checks (it runs as nagios user on system level) - it results in "No output from plugin"

It is because some temporary file is created during first step. To avoid problem just execute:
rm /tmp/*check_apachestatus_auto*