Apache monitoring from process to mod_status.

The collector verifies the httpd process is alive and reads mod_status for worker and request metrics. Those are the two layers where Apache problems live.

What RootTrace watches

Every reading is checked continuously; bad readings become grouped issues with the evidence attached. RootTrace also remembers whether it has seen the same incident before.

Process presenceapache2 and httpd both recognized; a dead server is an immediate issue.
mod_status metricsWorker states, request rates, and scoreboard-derived saturation.
Availability & latencyThe status endpoint itself checked for reachability and response time.

Warn and fail thresholds, prefilled

Sensible defaults out of the box, overridable per host with environment variables. No threshold spreadsheet required on day one.

Process death and status-endpoint failures drive severity
Status URL ROOTTRACE_APACHE_STATUS_URL

Setup

apache http server setup

$ export ROOTTRACE_APACHE_STATUS_URL='http://127.0.0.1/server-status?auto'

Read-only by architecture: no write path, no remediation executor, no inbound ports. Credential-like evidence is redacted before it leaves the host.

One collector, live in minutes

Everything on this page comes from the same read-only collector: one command per host, then point it at your targets.

install on any Linux host

$ # after adding the signed RootTrace dnf or apt repository:
sudo dnf install roottrace-collector  # apt: sudo apt install roottrace-collector
sudoedit /etc/roottrace/collector.env  # set ROOTTRACE_COLLECTOR_TOKEN and API URL
sudo roottrace-collector-setup apply
sudo systemctl enable --now roottrace-collector

Questions, answered honestly

What if mod_status is not enabled?

The process check still runs, so availability is covered. Enable mod_status on localhost to add worker and request metrics. The check supports basic auth if you protect it.

Is this safe to run next to production?

The collector is read-only by architecture, not by policy: there is no write path, no remediation executor, and no privileged mode to switch on. It sends short-lived outbound HTTPS requests, opens no inbound ports, and redacts credential-like evidence before anything leaves the host.

Do I need a separate agent for this?

No. One RootTrace collector per host covers every integration on this site: databases, web servers, containers, endpoints, and the Linux host itself, all from one signed package or container. You point it at targets with environment variables; there is nothing else to deploy.

Free on 5 hosts. Live in minutes.

Create a workspace, install one collector, and watch issues explain themselves.

Create free workspace Schedule a demo