Skip to main content
Redis supports coordination between exporter components running inside the monitored cluster. It is used by Metoro Exporter and Node Agent for shared cluster maps and related coordination data.

​
Talks To

​
How It Fits

Metoro Exporter and Node Agent both connect to Redis. The exporter syncs shared cluster maps through Redis, and node agents use the same coordination path while collecting and forwarding node-local telemetry. Redis is local to the monitored cluster exporter installation. It is not the durable telemetry store; telemetry still flows through Metoro Exporter to the hub ingester and is stored in ClickHouse on the hub side. The chart can run Redis as the default standalone deployment or as the redisCluster variant when that mode is enabled.

​
Operational Notes

Redis availability affects exporter coordination. If Redis is unavailable, exporter and node-agent components may be running but unable to share the coordination data they need. Operators should treat Redis as stateful local infrastructure for the exporter installation. The default chart path enables persistence for Redis, and Redis resource sizing should be considered alongside exporter and node-agent load. Losing Redis state is recoverable. Redis does not hold durable telemetry or control-plane metadata, and the shared maps it stores are rebuilt by exporter and node-agent components as they reconnect and observe the cluster again.