So when you set up Apache Monitoring, it’s not really as easy as they say.
Or more accurately, getting apache monitored is easy – setting the appropriate alerts is not always.
While Logicmonitor, referenced above, has sensible defaults based on Apache’s httpd default MaxClients, many sites have to tune the MaxClients (either to increase it, if they are serving mostly static content, or decrease it if serving with php, perl or other backends, due to memory/scalability issues.) Monitoring systems have no way of knowing what the real limit of an httpd server has been set to – and while it’s easy enough to adjust the thresholds in the monitoring system, I just wonder why mod_status does not report the configured limits of MaxClients (& ThreadsPerChild).
Then the monitoring systems could read this and set their thresholds appropriately, automatically. (At least decent ones like LogicMonitor could. Any monitoring system that can’t do calculated alert thresholds is not worth deploying, IMHO. )