Databases & queues

Redis monitoring that catches evictions before the cache lies.

A Redis at maxmemory quietly evicting keys looks healthy from the outside, until hit rates fall and databases take the load. The collector watches memory percentage, evictions, and the replication link so you hear about it first.

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.

Memory pressureUsed memory against maxmemory as a percentage, with warn/fail thresholds.
Evictions & expirationsEvicted and expired key counters: the signature of an undersized cache.
Keyspace hit ratioHits vs. misses, the number your response times depend on.
ReplicationRole, master link status, connected replicas, and seconds since last master IO.
ClientsConnected and blocked clients, plus rejected connections.
LatencyCommand round-trip in milliseconds.

Warn and fail thresholds, prefilled

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

Memory warn / fail percent ROOTTRACE_REDIS_MEMORY_WARN_PERCENT

Setup

redis setup

# after installing the collector package, point it at your instance:
$ export ROOTTRACE_REDIS_TARGETS='redis-1:6379'

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

Does it support AUTH?

Yes. Set the password in the collector environment and the check authenticates before reading INFO. Credentials never leave the host; only the derived metrics do.

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