Apache's mod_status allows you to take a look at how your Apache httpd server is running - you can see a snapshot of some basic stats of the server, and also the current status of each of the threads. There are two options that you can apply to the URL as you look at the page - a
refresh option to cause the page to update every so many seconds, and an
auto option which allows you to reformat the output suitable for automatic processing.
The Apache source download includes a Perl script that will collect the data from the auto report and log it to a file ... but the script is (currently) out of date as some of the field names have changed under it, and it could do with a lick of paint, or perhaps a complete rebuild.
OK ... I rebuilt it ;-) - see
[here] - it's a new logger that records far more information, including some wider server stats too
and that does mean that you should run it from the web server, not remotely, if you want useful information
Be default, mod_status is disabled. And even when enabled, you'll want to limit it to where it can access from ... it's fairly standard httpd configuration stuff. If you're not familiar with configurinbg httpd, we cover it on our
Linux Web Server course, and if you need some training on Linux too it's included in
Deploying LAMP.
(written 2010-10-25, updated 2010-10-26)
Associated topics are indexed under
A606 - Web Application Deployment - Apache httpd - log files and log tools [3984] 20 minutes in to our 15 minutes of fame - (2013-01-20)
[3974] TV show appearance - how does it effect your web site? - (2013-01-13)
[3670] Reading Google Analytics results, based on the relative populations of countries - (2012-03-24)
[3554] Learning more about our web site - and learning how to learn about yours - (2011-12-17)
[3491] Who is knocking at your web site door? Are you well set up to deal with allcomers? - (2011-10-21)
[3447] Needle in a haystack - finding the web server overload - (2011-09-18)
[3443] Getting more log information from the Apache http web server - (2011-09-16)
[3087] Making the most of critical emails - reading behind the scene - (2010-12-16)
[3027] Server logs - drawing a graph of gathered data - (2010-11-03)
[3019] Apache httpd Server Status - monitoring your server - (2010-10-28)
[1796] libwww-perl and Indy Library in your server logs? - (2008-09-13)
[1780] Server overloading - turns out to be feof in PHP - (2008-09-01)
[1761] Logging Cookies with the Apache httpd web server - (2008-08-20)
[1656] Be careful of misreading server statistics - (2008-05-28)
[1598] Every link has two ends - fixing 404s at the recipient - (2008-04-02)
[1503] Web page (http) error status 405 - (2008-01-12)
[1237] What proportion of our web traffic is robots? - (2007-06-19)
[376] What brings people to my web site? - (2005-07-13)
A692 - Web Application Deployment - Monitoring and load testing your server [2272] Monitoring and loading tools for testing Apache Tomcat - (2009-07-07)
[2082] Jmeter - a first test case - (2009-03-14)
[2080] Using ApacheBench and jconsole to test and monitor Tomcat - (2009-03-14)
[2079] Java - Memory Allocation and garbage collection - (2009-03-14)
[1718] Increasing Java Virtual Machine memory for Tomcat - (2008-07-24)
54cb
Some other Articles
Tuning Apache httpd and Tomcat to work well togetherSeventh day traveller on the six day railwayThe legal considerations of your web presence - revisitedLogging the performance of the Apache httpd web serverWell House Manor - the next six yearsAudio equipmentException handling in Perl - using evalWhat are .pid files?Children, zombies, and reaping processes