Documentation‎ > ‎Monitoring Agents‎ > ‎

Apache HTTP Server

Collects performance and statistics data from Apache (or Apache derived) web servers. Note that it requires configuration on the server in order to work (described below).


Local/Remote Modes

The agent supports both local and remote modes. Since by its nature it accesses the web server remotely, the most common deployment mode is local.


Supported Versions

Although this agent will work with a large number of custom Apache builds out there, it is primarily designed to work with Apache-derived servers embedded into application servers, such as Websphere or Oracle. It supports IBM Http Server versions 1.3.x, 2.0.x and 6.0.x, and Oracle Http Server.


Configuration

Before running the web server, the following changes have to be made to Apache's httpd.conf file:
Uncomment (if necessary) the line which loads the mod_status.so module.
Uncomment (if necessary) the line which adds the mod_status.c module.
Check that location /server-status is defined and access to it is allowed. If security is not a concern, then access can be set as in the following example:

<Location /server-status>
SetHandler server-status
Order allow,deny
Allow from all
</Location>
Make sure that ExtendedStatus is set to On.
To verify that the above settings have been performed correctly, check that the following page loads in a web browser: http://[servername]:[port]/server-status
The agent itself supports the following configuration parameters:
Port: the TCP/IP port on which Apache web server is waiting for clients.


Contents

The agent provides the following information:
Servers: contains details about the workers which serve incoming HTTP requests.
Requests: holds statistics for HTTP requests processed by all workers in this web server.
Status: shows generic information about Apache's activity.


Screenshots