Linux hosts

Every Linux vital, from one collector.

One signed package turns on the checks an SRE would write by hand: the standard vitals plus the ones that actually explain incidents (I/O await, TCP retransmits, OOM kills, failed systemd units, and clock drift).

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.

CPU, memory, swapUsage with warn/fail thresholds prefilled per check.
Disk & inodesCapacity and inode exhaustion per filesystem: the classic silent killer.
Disk I/OAwait times, utilization percentage, and per-device throughput.
Network healthRetransmits, drops, ephemeral-port usage, and per-interface throughput.
Kernel & OOM eventsOOM kills and I/O errors read from the kernel log, as issues with evidence.
systemd & processesFailed units, timers, watched processes, and time drift.

Warn and fail thresholds, prefilled

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

Every check ships warn / fail defaults, overridable per host via environment variables

Setup

linux hosts setup

# the whole setup:
# 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

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 distributions are supported?

Modern systemd-based distributions, including RHEL 9/10, Rocky Linux, CentOS Stream, Debian, and Ubuntu. The installer sets up a systemd service and the collector runs as a normal outbound-only process.

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