When it's their outage, know in one glance.

Half of 3 a.m. debugging ends at a vendor's status page. The collector watches the pages you list and raises their reported incidents as signals, so 'is it us or them?' is answered on the same dashboard as everything else.

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.

Status indicatorThe page's own severity indicator (minor, major) captured as it changes.
Incident descriptionThe vendor's description in the evidence, not just a color.
Reachability & latencyThe status page itself checked for availability 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.

Vendor-reported indicators drive severity
Check timeout seconds ROOTTRACE_STATUS_PAGE_TIMEOUT_SECONDS

Setup

vendor status pages setup

$ export ROOTTRACE_STATUS_PAGES='https://status.vendor.example,https://status.cloud.example'

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

Which status page formats work?

Pages exposing the common status JSON format (indicator plus description, as popularized by Statuspage-style APIs). Point it at the page's API URL and the indicator lands in the evidence.

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