Endpoints & certificates

Uptime, latency, and the certificate that expires next Tuesday.

Point the collector at your endpoints: it checks status codes, latency against warn/fail budgets, and expected body content. It also watches TLS certificates, so expiry is a calm warning weeks out, not a Saturday page.

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.

HTTP endpoint checksStatus code, latency in milliseconds, and optional expected-body matching per target.
Latency budgetsSeparate warn and fail thresholds in milliseconds, per endpoint.
TLS certificate expiryDays remaining, issuer, and subject. Warn and fail day thresholds prefilled.
Ping & DNSICMP and resolution checks for the layer under HTTP.

Warn and fail thresholds, prefilled

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

Latency warn / fail ms ROOTTRACE_HTTP_LATENCY_WARN_MS
Certificate fail days ROOTTRACE_TLS_FAIL_DAYS

Setup

http & tls setup

$ export ROOTTRACE_HTTP_TARGETS='https://app.example.com/health'
$ export ROOTTRACE_TLS_TARGETS='app.example.com:443'

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

Can TLS targets come from my HTTP targets automatically?

Yes. The collector can derive certificate checks from your configured HTTP targets, so both stay in sync from one list.

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