Redis monitoring with Topologix

Data & Storage

Redis server and cluster statistics from a single INFO call per poll — memory, hit ratio, ops/sec, replication health, persistence, and per-database keyspace. Flip on cluster fanout and the same source aggregates every node of a Redis Cluster.

Requirements

  • Network reach from the Topologix server or a proxy agent to the Redis port (default 6379; 6380 on TLS-enabled builds).
  • Credentials are optional: with requirepass, fill in only the password; for Redis 6+ ACLs, a dedicated user with +info +@connection (use +@dangerous if you hit NOPERM errors).
  • For cluster fanout, every node’s address must be reachable — clusters in Kubernetes / Docker / NAT need a proxy agent on the Redis network, because CLUSTER NODES returns internal addresses.

1 · Set up the integration

  1. Open the Integrations pageClick Integrations in the toolbar and pick Redis from the catalogue.
  2. Enter host and portPlus optional Username and Password — leave the username blank for Redis 5 or the default ACL user.
  3. Pick the togglesUse TLS (rediss://) and Allow self-signed TLS certificates as needed; tick Fan out to all cluster nodes when pointing at a Redis Cluster member.
  4. Create, then verifyClick Create, then reopen the integration and click Test — it reports the Redis version, role, and connected clients; in fanout mode, node reachability, the master/replica breakdown, and slot health.
The integration catalogue — Redis found via search.
The integration catalogue — Redis found via search.
The Redis configuration drawer with example values. Every screen in this guide is the real product.
The Redis configuration drawer with example values. Every screen in this guide is the real product.
Target on a private network? Route it through a proxy agent. Proxy agents run inside your network — behind NAT, on a management VLAN, in an air-gapped segment — and reach targets the Topologix server can't. The agent polls the server every 15 seconds for its assignments, runs the checks locally, and pushes results back every 5 seconds, so no inbound firewall rules are ever needed. Set a default proxy on the integration; every metric source can override it. If a proxy goes offline, its sources are marked stale within ~90 seconds and the last known values stay visible.

2 · Add it to a flow

  1. Select the cache nodeClick the node, open Metrics, then + Add and choose the Redis integration.
  2. Add the sourceNo per-type options — one source covers the whole server (or, with fanout, the whole cluster).
  3. SaveSet the interval and click Add Source. The card shows memory, hit ratio, ops/sec, replication and keyspace; fanout adds aggregate totals plus a per-node drill-down.
The add-source form with the integration selected and its per-type options loaded.
The add-source form with the integration selected and its per-type options loaded.
The live card on the canvas — latest value, label, and sparkline, updating on the source’s interval.
The live card on the canvas — latest value, label, and sparkline, updating on the source’s interval.

Good to know

  • Each poll is one INFO call — O(1), no impact on production traffic. Auth failures come back with the real reason (WRONGPASS vs. NOPERM, with the exact ACL grant to add).
  • Cluster fanout runs CLUSTER NODES against the seed, then polls INFO from every discovered node in parallel; nodes that drop out are reported as unreachable rather than silently vanishing.
  • Pointing a non-fanout source at a cluster member still works for per-node stats — the fetcher tells you when Redis reports moved slots.

All integrations →

See it on your own infrastructure

Book a demo and we will walk you through Topologix with your systems in mind: on our cloud, or self-hosted in your own network.

Book a demoContact us