Redis Monitoring

redis is an in memory data structure store commonly used as a database, cache, and message broker it is designed for high performance and low latency, making it suitable for real time applications such as caching, session management, analytics, messaging queues, and leaderboards redis supports multiple data structures and offers features such as persistence, replication, and clustering for scalability and high availability redis monitoring in kloudmate helps you observe the health, performance, and behavior of your redis servers by collecting metrics using the kloudmate agent powered by opentelemetry this enables centralized monitoring of redis instances running on cloud virtual machines or on premise servers what this integration provides with redis monitoring enabled, kloudmate collects telemetry that provides visibility into command execution and throughput memory usage and fragmentation client connections and blocked clients network input and output replication and persistence behavior redis server uptime and cpu time this visibility helps detect performance degradation, memory pressure, command latency issues, connection limits, and replication problems configuring redis metrics collection you can achieve redis performance monitoring by using the kloudmate agent, which automatically collects redis metrics and sends them to kloudmate for analysis and visualization if you are already running the kloudmate agent and want to configure it to send redis telemetry data to kloudmate, update your yaml configuration as shown below agent configuration extensions health check pprof endpoint 0 0 0 0 1777 zpages endpoint 0 0 0 0 55679 receivers otlp protocols grpc http redis endpoint localhost 6379 collection interval 10s processors resourcedetection detectors \[env, system] cumulativetodelta batch send batch size 5000 timeout 10s exporters otlphttp endpoint 'https //otel kloudmate com 4318' headers authorization \<token> service pipelines metrics receivers \[otlp, opencensus, prometheus, redis] processors \[cumulativetodelta, batch, resourcedetection] exporters \[otlphttp] extensions \[health check, pprof, zpages] post integration data validation verify that redis metrics are flowing into kloudmate using the explore view after the agent restarts log in to your kloudmate account navigate to explore select opentelemetry – metrics choose a redis metric exposed by the integration click run query to view time series data seeing data confirms that redis telemetry is being collected successfully redis metrics name description redis commands number of commands processed per second redis cmd latency command execution latency redis memory used total number of bytes allocated by redis using its allocator redis memory fragmentation ratio ratio between used memory rss and used memory redis clients connected number of client connections (excluding connections from replicas) redis keys evicted number of evicted keys due to maxmemory limit redis net input the total number of bytes read from the network redis net output the total number of bytes written to the network redis replication offset the server’s current replication offset redis uptime number of seconds since the redis server started for the complete redis metrics list, refer to the https //github com/open telemetry/opentelemetry collector contrib/blob/main/receiver/redisreceiver/documentation md