Databases & queues

ClickHouse monitoring, deliberately light.

ClickHouse rarely needs deep babysitting; it needs someone to notice when it stops answering or starts queueing. The collector runs a light HTTP health check: reachability, latency, version, and active queries.

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.

AvailabilityHTTP health endpoint reachability, as its own issue when it fails.
LatencyRound-trip in milliseconds, trended.
Active queriesConcurrent query count: the early sign of a stuck workload.
VersionReported for context, so a surprise upgrade shows in the evidence.

Warn and fail thresholds, prefilled

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

Reachability and latency drive severity

Setup

clickhouse setup

# after installing the collector package, point it at your instance:
$ export ROOTTRACE_CLICKHOUSE_URL='http://clickhouse-1:8123'

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

Why so light?

Because most ClickHouse pages are 'it is down' or 'it is drowning', and both show up in reachability, latency, and active queries. Deeper application-level signals belong in APM, which RootTrace also provides.

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