Redis Insight is a robust platform for monitoring, visualizing, and optimizing Redis environments across Redis Cloud, Redis Software, and open-source deployments. This knowledge base article provides step-by-step instructions, troubleshooting guidance, and actionable best practices for performance monitoring. It also includes a Performance Metrics Cheat Sheet for quick reference, plus references to advanced observability tools for production environments.
Performance Metrics Cheat Sheet
Metric |
Redis Cloud |
Redis Software |
|---|---|---|
Latency (avg) |
< 1 ms |
< 1 ms |
Cache Hit Rate |
50–80%+ (caching workloads) |
50–80%+ (caching workloads) |
Memory Utilization |
Stay within 20-80% of plan allocation |
Stay within 20-80% of node RAM; avoid swap |
CPU Usage |
< 70% sustained per shard |
< 70% sustained per core |
Connections |
Monitor for sudden spikes or leaks; check client pooling |
Same; adjust |
Evictions |
Investigate any unexpected spikes |
Investigate any unexpected spikes |
Slow Log Events |
Capture blocking ops; avoid KEYS, unbounded HGETALL/SCAN |
Same, plus review for shard imbalance |
Hot Keys |
Identify with Insight Profiler; shard or cache locally |
Same; consider manual hash tagging |
Query Engine Throughput |
Use Query Performance Factor; optimize indexes |
Same; follow RQE best practices |
Key Capabilities of Redis Insight for Performance Monitoring
Redis Insight’s real-time command profiler, memory and data type database analysis tools, Slow Log viewer, and visual dashboards give you direct insight into latency, throughput, memory usage, and connections. It also supports stream monitoring, Prometheus/Grafana integration, and bulk key management for proactive optimization (Redis Insight documentation).
Step-by-Step: Monitoring Redis Performance with Redis Insight
1. Installation and Setup
-
Download and Install
Redis Insight is available for Windows, macOS, Linux, Docker, Kubernetes, and AWS EC2 (installation guide).
-
Launch and Connect Database
Use the Add Database workflow, enter host/IP, port, credentials, and enable TLS if required. Test connectivity before saving.
For cloud users, ensure your public IP is allow-listed or private networking is configured.
2. Using Core Performance Monitoring Tools
-
Profiler
View real-time command timelines, identify high-frequency operations, and analyze client behavior.
-
Database Analysis
Visualize data type breakdown and memory distribution, and identify top keys by size, namespace, and expiration (database analysis best practices).
-
Slow Log Analysis
Inspect blocking or slow commands such as SCAN/KEYS and HGETALL on large datasets; adjust the slowlog threshold as needed.
-
Monitoring Streams
Track Redis Streams and consumer groups for pending entries and throughput issues.
-
Command Line & Workbench
Use the integrated CLI or Workbench for advanced queries, with schema-aware autocomplete and inline help.
3. Integrating with External Monitoring Tools
For production observability, connect Redis Software metrics to Prometheus and Grafana (Prometheus & Grafana integration guide).
Use the v2 Prometheus endpoint (
https://<db-host>:8070/v2) for real-time metrics.Import the official Grafana dashboards for clusters, nodes, databases, and shards.
Third-party monitoring like Datadog and Dynatrace are also supported.
Performance Monitoring Best Practices
-
Monitor Key Metrics
CPU (<70% sustained), memory usage (20–80%), latency (<1 ms average), cache hit rate (>50–80%), eviction spikes, connection growth, and slowlog events.
-
Avoid Blocking Commands
Replace
KEYSwithSCAN, useUNLINKfor large deletions, and limit unbounded range queries (query performance tuning guide).
-
Optimize Query Engine Workloads
Use TAG indexes where possible, avoid wildcards, and ensure only necessary fields are included in indexes.
-
Use Database Analysis Regularly
Detect hot keys, large keys, and memory hotspots early to prevent performance degradation.
-
In Kubernetes
Follow the official Redis Insight on Kubernetes deployment guidelines for resource allocation and monitoring.
Troubleshooting Common Performance Issues
Issue |
Cause/Indicator |
How to Investigate/Fix |
|---|---|---|
High latency |
CPU spikes, blocking commands, swap, network |
Analyze slow logs; check resource usage; avoid blocking ops; add shards if needed. |
Memory overuse/evictions |
Used > 80% memory, high eviction rates |
Optimize data model; configure eviction policies; monitor with database analysis. |
Dropped/failed connections |
Max client limits, firewall, client config |
Tune maxclients; pool connections; check firewall; verify in Slow Log and Profiler. |
“Hot key” causing bottlenecks |
Most ops on one key across cluster |
Use |
Slow, blocking deletions |
Using DEL on large keys |
Switch to UNLINK or use Bulk Actions in Redis Insight. |
Index/query scalability (RQE) |
Inefficient schema, large result sets |
Refine indexes and queries (see Best Practices above). |
Monitoring Gaps in K8s |
Missing/poorly configured exporters |
Deploy Prometheus Operator & ServiceMonitor; secure endpoints; import official dashboards. |
0 comments
Please sign in to leave a comment.