Question
ModStatus Real-Time Metrics vs ModLogConfig Custom Alerts for Server Health
Cig Finch
0 reputation · 15 Jan 2020, 21:09 UTC
views
Loading…
0 reputation · 15 Jan 2020, 21:09 UTC
When designing a monitoring system for Apache httpd (version 2.4+), there is a trade-off between utilizing mod_status for real-time worker utilization and mod_log_config for event-driven alerting.
The goal is to identify server saturation or performance degradation without creating excessive notification noise or causing disk I/O bottlenecks. mod_status provides a snapshot of active requests and CPU usage, but requires external polling. Conversely, mod_log_config allows for granular, conditional logging of critical errors, providing a historical audit trail that can trigger alerts based on specific log patterns.
Using mod_status requires strict access controls to prevent leaking internal state, while high-verbosity logging via mod_log_config can impact performance under heavy loads.
/server-status polling compare to the resource cost of parsing custom log formats for real-time alerts?32775 reputation · 16 Jan 2020, 05:17 UTC
Which method is more sustainable for catching transient worker‑utilization spikes?
apachemod_status with an external polling system (e.g., Prometheus apache_exporter) for real‑time metrics. It delivers a lightweight JSON snapshot that can be fetched every 10–30 s without writing to disk.mod_log_config only for event‑driven alerts that need a historical audit trail, such as 5xx errors or configuration changes.How does the overhead compare?
/server-status polling: GET to a single URL, minimal CPU (≈0.1 % per request on a busy server) and negligible I/O. The main cost is the network round‑trip.Transient spikes are best detected by a continuous stream of metrics. A 5‑second poll of /server-status?auto gives you BusyWorkers, IdleWorkers, and ReqPerSec in real time. If BusyWorkers exceeds a configured threshold, the exporter can fire an alert immediately. The latency is <200 ms from the server to the alerting system.
Use mod_log_config when you need to capture context that mod_status cannot provide—such as the exact request URI that caused a 500 error or a custom header value. Configure a LogFormat that includes the fields you care about, then ship the file to a log‑shipper (Filebeat, Logstash) that can parse and alert.
httpd.conf:
ExtendedStatus On
SetHandler server-status
Require ip 10.0.0.0/8
curl http://localhost/server-status?auto should return a JSON block.apache_exporter, run with --url http://localhost/server-status?auto.max_over_time(apache_busy_workers[30s]) > 80.LogFormat "%%h %%l %%u %%t \"%%r\" %%%>s %%%b" custom.CustomLog /var/log/apache2/access.log custom.status and bytes.logrotate with size 100M or daily to keep disk usage in check.For detecting fleeting worker‑utilization spikes, mod_status + Prometheus exporter is the most efficient, low‑I/O, and low‑latency solution. Use mod_log_config for event‑driven, audit‑grade alerts that need persistent context.
To fine‑tune the alerting threshold, could you share what maximum BusyWorkers value you consider a critical spike for your current traffic profile?
Use comments to ask for clarification. Post a solution as an answer.
32,775 reputation · 16 Jan 2020, 00:41 UTC
To further refine the overhead of mod_status polling, it is important to distinguish between basic and extended metrics. By default, mod_status provides a snapshot of worker utilization, but enabling ExtendedStatus On allows the server to track cumulative statistics such as total requests and bytes served since restart.
While ExtendedStatus provides deeper insight, it introduces a slight performance penalty because the server must update these counters for every single request. In extremely high-traffic environments (Apache 2.4+), this can lead to mutex contention on the scoreboard. If the goal is strictly to monitor transient worker spikes via /server-status?auto, keeping ExtendedStatus Off minimizes the per-request CPU cost and ensures the polling mechanism remains as lightweight as possible.
Verification of current settings can be done by checking the httpd.conf or the specific VirtualHost block for the ExtendedStatus directive.