Databases & queues

Cassandra monitoring across every contact point.

The collector connects to your contact points read-only, verifies system table health, and reports peers, datacenter, and rack, so a node quietly missing from the ring is an issue, not a discovery during an incident.

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.

Reachability & latencyConnection health to each contact point in milliseconds.
Peer countNodes visible in the ring. A shrinking count is the headline.
System table healthRead checks against system tables to confirm the node actually serves queries.
Topology contextCluster name, datacenter, rack, and release version 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 system-table reads drive severity

Setup

cassandra setup

# after installing the collector package, point it at your instance:
$ export ROOTTRACE_CASSANDRA_CONTACT_POINTS='cassandra-1,cassandra-2'

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 auth modes are supported?

Username and password via collector environment variables, with configurable port, local datacenter, and connect timeout.

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