Skip to main content
The Redis Overview dashboard provides real-time monitoring of your Redis servers. View performance metrics, memory usage, key distribution, and connected clients from a single page.

​
Key Concepts

Connection

A configured Redis server endpoint. Supports standalone, Sentinel, and cluster deployments.

Database

Redis organizes keys into numbered databases (0-15 by default). Each database is isolated.

Client

An active connection to Redis. Includes your application connections and admin tools.

Memory

Redis stores all data in memory. Monitor usage to prevent out-of-memory conditions.

​
Required Permissions

​
Connection Types

​
How to Select a Connection

1

Open Overview Page

Navigate to Redis > Overview.
2

Choose Connection

Use the connection dropdown to select from your configured Redis connections.
3

View Dashboard

The dashboard loads automatically with server statistics and connected clients.
Your last selected connection is remembered. The page will automatically reconnect on your next visit.

​
How to Refresh Dashboard Data

1

Click Refresh

Click the refresh button in the toolbar to reload all dashboard data.
2

View Updated Stats

All metrics, memory stats, and client list update with current values.

​
Understanding Dashboard Metrics

​
Server Information

​
Memory Usage

If memory usage approaches max memory, Redis may evict keys or reject writes depending on the eviction policy.

​
Fragmentation Ratio

​
Performance Statistics

Blocked clients are normal when using commands like BLPOP, BRPOP, or XREAD. Persistent high blocked counts may indicate slow consumers.

​
Understanding Key Distribution

The dashboard shows key counts by data type:

​
Understanding Replication

​
Persistence Types

​
How to View Connected Clients

1

Scroll to Connected Clients

The client list appears at the bottom of the dashboard.
2

Search Clients

Use the search box to filter by address, name, or command.
3

Review Client Details

Each client shows address, name, database, current command, age, and idle time.

​
Client Flags

​
Troubleshooting

  • No active Redis connections are configured
  • Navigate to Settings > Integrations to add a Redis connection
  • Verify connection settings (host, port, authentication)
  • Verify Redis server is running
  • Check network connectivity to the Redis host
  • Confirm authentication credentials are correct
  • Ensure TLS settings match server configuration
  • Check for keys without TTL that should expire
  • Review max memory policy (eviction settings)
  • Consider enabling memory analysis with MEMORY DOCTOR
  • Check for memory fragmentation
  • Restart Redis to defragment memory
  • Enable active defragmentation in Redis 4+
  • Check for patterns causing fragmentation (large key deletions)
  • Consider memory allocator tuning
  • Check maxclients configuration
  • Review if clients are closing connections properly
  • Ensure connection pooling is used in applications
  • Check for connection leaks
  • Verify the selected connection is active
  • Check if the Redis server allows INFO command
  • Ensure your user has read permission
  • Try refreshing the page

​
FAQ

Used Memory is what Redis has allocated for data. Max Memory is the configured limit (0 means no limit). When used memory reaches max memory, Redis applies the eviction policy to free space.
Peak memory shows the highest memory usage since server start. Memory decreases when keys expire or are deleted. Large temporary operations can spike peak memory.
Operations per second measures the instantaneous rate of Redis commands being processed. This includes all operations: reads, writes, and admin commands.
Each database (0-15) is a separate keyspace. Keys in database 0 are independent from keys in database 1. Databases share the same Redis instance and memory.
Clients become blocked when using blocking commands like BLPOP, BRPOP, XREAD, or WAIT. They remain blocked until data becomes available or timeout expires.
The client list is paginated for performance. Use search to find specific clients by address or name. Very large deployments may have thousands of connections.
RDB creates point-in-time snapshots at intervals. AOF logs every write operation. RDB is faster for recovery; AOF provides better durability. Production systems often use both.
For a master, check that expected replicas appear in “Connected Slaves”. For a replica, the role should show “slave” with link status “up”. Replication lag should be minimal.

​
Best Practices

​
Regular Monitoring

  • Check memory usage trends before reaching limits
  • Monitor rejected connections to detect capacity issues
  • Track ops/sec during peak hours for capacity planning
  • Review fragmentation ratio periodically

​
Memory Management

  • Set appropriate maxmemory limits in production
  • Configure eviction policies based on your use case
  • Use TTL on cache keys to prevent unbounded growth
  • Monitor expiring keys count

​
Connection Management

  • Use connection pooling in applications
  • Set appropriate connection timeouts
  • Close idle connections to free resources
  • Monitor client count during deployments

​
Performance Tuning

  • Review slow log for optimization opportunities
  • Check key distribution for hot spots
  • Consider clustering for high-throughput workloads
  • Monitor blocked clients for queue processing issues