Rehearse the user journey before a user fails it.

Journeys are step files the collector replays continuously: API journeys chain HTTP steps, and browser journeys drive a real page with goto, click, fill, wait, and assert-text steps. When one breaks, the issue names the failing step, not just the journey.

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.

API journeysMulti-step HTTP flows with per-journey latency and the failing step named.
Browser journeysScripted goto / click / fill / wait-for / assert-text steps with per-step durations.
Latency budgetsWarn and fail thresholds in milliseconds for both journey types.
Step-level evidenceStep counts, the step that failed, and what it saw. Debugging starts at the right line.

Warn and fail thresholds, prefilled

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

Synthetic latency warn / fail ms ROOTTRACE_SYNTHETIC_LATENCY_WARN_MS
Browser latency warn / fail ms ROOTTRACE_BROWSER_LATENCY_WARN_MS

Setup

synthetic monitoring setup

$ export ROOTTRACE_SYNTHETIC_JOURNEYS_PATH='/etc/roottrace/journeys'
$ export ROOTTRACE_BROWSER_JOURNEYS_PATH='/etc/roottrace/browser-journeys'

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

Where do journeys run?

On your own hosts, from the collector. They test the path your users and services actually take, and internal apps are reachable without opening anything to a probe network.

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