INFO
INFO returns everything about your Valkey/Redis server - memory, CPU, clients, replication, and more. Essential for monitoring and debugging.
You'll Learn
- INFO command sections
- Key metrics to monitor
- Memory usage analysis
- How Redimo visualizes server stats
See Your Data, Not Terminal Text
Redimo visualizes every Redis data type beautifully. Edit inline, undo mistakes, stay safe in production.
1. What Is INFO?
INFO returns a comprehensive report of server statistics organized into sections. You can request all sections at once or specific ones. It's the foundation of Redis monitoring.
Unlike most Redis commands, INFO returns a multi-line text response rather than a structured data type. Each line follows the format key:value, grouped under section headers.
Syntax
INFO # All sections
INFO server # Server info (version, uptime, mode)
INFO memory # Memory usage and fragmentation
INFO clients # Connected clients info
INFO stats # General statistics (ops, hits, misses)
INFO replication # Master/replica status
INFO keyspace # Database key counts
INFO cpu # CPU usage
INFO cluster # Cluster status (if enabled)Common Sections
server- Version, uptime, modememory- RAM usage, fragmentationstats- Ops/sec, hit rateskeyspace- Key counts per DB
Use INFO For
- • Monitoring memory pressure
- • Debugging performance issues
- • Checking replication status
- • Verifying server configuration
2. The CLI Way (Hard Mode)
INFO dumps hundreds of lines of text. Finding the metric you need is like searching for a needle in a haystack:
Full INFO Output (Truncated)
127.0.0.1:6379> INFO
# Server
redis_version:7.2.3
redis_git_sha1:00000000
redis_git_dirty:0
redis_mode:standalone
os:Linux 5.15.0-91-generic x86_64
arch_bits:64
uptime_in_seconds:1234567
uptime_in_days:14
# Clients
connected_clients:42
blocked_clients:3
tracking_clients:0
# Memory
used_memory:1073741824
used_memory_human:1.00G
used_memory_rss:1181116416
used_memory_rss_human:1.10G
used_memory_peak:1288490188
used_memory_peak_human:1.20G
mem_fragmentation_ratio:1.10
... (200+ more lines)Filtering with grep
127.0.0.1:6379> INFO memory | grep used_memory_human
# Doesn't work! Redis CLI doesn't support piping
# From shell:
$ redis-cli INFO memory | grep used_memory_human
used_memory_human:1.00G
$ redis-cli INFO stats | grep instantaneous_ops
instantaneous_ops_per_sec:12345The Problem
3. The Redimo Way (Smart Mode)
Redimo parses INFO and displays the most important metrics in a visual dashboard. Memory usage as a progress bar. Key counts per database. Uptime formatted as human-readable duration.
What Redimo Does for Server Info:
- ●Visual Dashboard: Key metrics displayed as cards with labels. No text parsing required.
- ●Memory Progress Bar: See used vs available memory at a glance. Color-coded warnings when approaching limits.
- ●Server Type Detection: Automatically detects Redis vs Valkey and shows the version prominently.
- ●Keyspace Summary: Shows key count and expiring keys per database in a clean table.
- ●Connection on Connect: Server info is fetched and displayed immediately when you connect.
CLI Pain Points
- • Wall of unformatted text
- • Manual metric hunting
- • No visual indicators
- • No historical tracking
- • Must grep for specific values
Redimo Solutions
- • Visual dashboard cards
- • Key metrics highlighted
- • Memory progress bar
- • Database key counts
- • Auto-refresh on connect
4. Key Metrics to Monitor
Not all INFO metrics are equally important. Here are the ones you should watch:
| Metric | Section | What It Means |
|---|---|---|
used_memory_human | memory | Current memory usage |
mem_fragmentation_ratio | memory | Should be ~1.0 (>1.5 = fragmentation issue) |
instantaneous_ops_per_sec | stats | Current throughput |
connected_clients | clients | Active connections |
blocked_clients | clients | Clients waiting on BRPOP, etc. |
keyspace_hits/misses | stats | Cache hit rate calculation |
Fetching Specific Metrics
# Memory overview
INFO memory | grep -E "used_memory_human|mem_fragmentation|maxmemory"
# Performance stats
INFO stats | grep -E "ops_per_sec|keyspace_hits|keyspace_misses"
# Client health
INFO clients | grep -E "connected_clients|blocked_clients"
# Keyspace (keys per database)
INFO keyspace
# db0:keys=12345,expires=1234,avg_ttl=36000005. Warning Signs
Learn to spot problems before they become outages:
mem_fragmentation_ratio > 1.5
Redis is using more memory than it should. Caused by many small allocations/deallocations. Fix: restart Redis or use MEMORY PURGE.
used_memory approaching maxmemory
When Redis hits maxmemory, it starts evicting keys (if policy allows) or rejecting writes. Monitor this closely.
blocked_clients staying high
Clients waiting on blocking commands (BRPOP, BLPOP). Could indicate slow consumers or missing producers.
Low hit rate (keyspace_hits / (hits + misses))
Cache isn't being effective. Review TTLs, cache warming strategy, or key design.
6. Pro Tips
INFO is Cheap
Useful Monitoring Commands
# Calculate cache hit rate
# hit_rate = keyspace_hits / (keyspace_hits + keyspace_misses)
# Check memory policies
CONFIG GET maxmemory
CONFIG GET maxmemory-policy
# Monitor in real-time (press Ctrl+C to stop)
redis-cli --stat # Shows ops/sec, memory, clients
# Slow log (commands taking longer than threshold)
SLOWLOG GET 10
CONFIG GET slowlog-log-slower-than # Default: 10000 (10ms)
# Memory analysis
MEMORY DOCTOR # Redis 4.0+, suggests optimizations
MEMORY STATS # Detailed memory breakdownRedimo Bonus
Ready to Monitor?
Stop parsing INFO output in your terminal.
Download Redimo and see server stats at a glance.