Web servers & load balancers

HAProxy monitoring per frontend, per backend.

The collector reads the HAProxy stats CSV and turns per-proxy state into issues: a backend with no healthy servers is named, not averaged away.

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 presenceA dead load balancer is the first thing you want paged on.
Backend healthPer-backend status from the stats endpoint, with failing backends named.
Session & traffic countersSessions and rates per frontend and backend.

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 down backends drive severity
Stats URL ROOTTRACE_HAPROXY_STATS_URL

Setup

haproxy setup

$ export ROOTTRACE_HAPROXY_STATS_URL='http://127.0.0.1:8404/stats;csv'

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

Does it support the stats page behind auth?

Yes. Basic-auth credentials go in collector environment variables and are used only for the local stats request.

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