Monitoring

Apache

In order for ActiveDiscovery to detect a web server is using Apache, and to be able to collect statistics, LogicMonitor must be able to pull the /server-status page, which is served by the mod_status module.  By default, Apache does not allow access to this page.

If your servers are not having Apache monitoring discoverd automatically, it is likely that the collector cannot access the server-status page. Ensure Apache is loading the mod_status module, and that the Apache configuration file is set to allow the collector to pull the server status page, by a section such as the following in the httpd.conf.

<IfModule mod_status.c>
ExtendedStatus On

<Location /server-status>
SetHandler server-status
Order Deny,Allow
Deny from all
Allow from localhost 10.0.0.12
</Location>
</IfModule> 

substituting 10.0.0.12 for the IP address of the device where the collector is installed.

Apache will need a graceful restart after the config file has been changed.

You can test that Apache is set up correctly by attempting to load the server status page from the collector.

e.g.

telnet 10.0.0.100 80
GET /server-status HTTP/1.0 
<cr> 
 

No Redirects

One point to note is that you should not be getting the results of /server-status from a redirect, but must get it directly from the queried server. (LogicMonitor will not follow such redirects, as we want to be sure we are monitoring Apache response on the server being initially queried, not a possibly different server that is redirected to.)

If you are using rewrite rules, one way to ensure that the /server-status page is not being redirected is to insert the following immediately after enabling the rewrite engine:

# don't rewrite /server-status
RewriteRule .*server-status.* - [L]