Troubleshooting the Apache Monitor

How to Troubleshoot the Apache Monitor

How it Works

Essentially the Apache Server Monitor is a URL Content Monitor designed to work specifically against the Apache server-status page. This page may not be enabled on the Apache server by default. See the Apache Web Server documentation for information on enabling this.

The counter list comes from the SiteScope templates.applicationscounters.apache file. Some counters are available only on the Unix release of Apache, the rest are available on both Unix and Windows.

Selecting the counters from this list tells SiteScope which values to report on. SiteScope builds a regular expression dynamically, depending on which counters are selected.

How to Troubleshoot

1) First try bringing up the server-status page in a regular browser:


For an example of what a status page looks like see Apache’s web site here:

If this is page is not available then the SiteScope monitor will not work. The server-status page must be enabled in Apache.

2) If the server-status page is available from outside of SiteScope but the SiteScope monitor is failing with an error like unable to connect to server or unable to reach server then check to see if possibly a proxy server is required. You can add configuration for a proxy server under the Advanced Options section of the monitor definition. Format for specifying a Proxy is:

3) A username and password might be required to access the server-status page – this can also be configured in the Advanced Options section of the monitor.

4) From the Apache Web Server documentation:

Note that mod_status will only work when you are running Apache in standalone mode and not inetd mode.

This goes back to the requirement of the monitor – the server-status page must be enabled. If it can’t be enabled due to the server running in inetd mode then the Apache monitor will not work (because the page won’t be available in Apache).

Leave a Comment