Redis Integration
Monitor keyspace metrics, command latency, memory fragmentation, and replication health across your Redis deployments. Correlate cache behavior with application performance traces.
How It Works
Enable Redis Monitoring
Add a single CONFIG SET command to your redis.conf or run it live. The TigerOps Redis exporter connects over the standard Redis protocol — no agent installation on the host required.
Deploy the Exporter
Run the TigerOps Redis exporter as a sidecar or standalone container. It auto-discovers all keyspaces, replica nodes, and cluster shards using the CLUSTER NODES command.
Configure Alert Thresholds
Set thresholds for memory usage percentage, eviction rate, hit rate drop, and latency percentiles. TigerOps applies intelligent defaults based on your observed baseline.
Correlate with Application Traces
TigerOps links Redis latency spikes to the specific application service requests that caused them, giving you full end-to-end context from cache miss to slow user response.
What You Get Out of the Box
Keyspace & Hit Rate Metrics
Per-database keyspace size, key expiry rates, hit/miss ratios, and eviction counts. Drill into which keyspaces are under memory pressure with AI-driven recommendations.
Command Latency Percentiles
P50, P95, and P99 latency per command type using Redis LATENCY HISTORY. Identify slow commands, large key scans, and blocking operations before they cascade.
Memory Fragmentation Analysis
Track RSS vs used memory, fragmentation ratio, and allocator overhead. TigerOps alerts when fragmentation degrades performance and suggests MEMORY PURGE timing.
Replication Lag
Monitor master-replica replication lag in bytes and seconds for all replica nodes. TigerOps fires early alerts when replication falls behind and identifies the cause.
Cluster Shard Health
For Redis Cluster deployments: per-shard key distribution, slot migration status, failover events, and cross-shard rebalancing metrics.
Slow Log Ingestion
TigerOps ingests the Redis SLOWLOG and correlates slow commands with application traces, making it easy to identify which service triggered a blocking operation.
redis.conf for TigerOps
Add these settings to your redis.conf to enable latency monitoring and keyspace notifications.
# TigerOps Redis monitoring configuration
# Add to redis.conf or apply via CONFIG SET
# Enable latency monitoring (tracks commands >1ms)
latency-monitor-threshold 1
latency-tracking yes
latency-tracking-info-percentiles 50 95 99
# Enable keyspace notifications for TigerOps event correlation
# K = keyspace events, E = keyevent events
# x = expired events, e = evicted events, g = generic commands
notify-keyspace-events "KExeg"
# Slow log for command analysis (threshold in microseconds)
slowlog-log-slower-than 10000
slowlog-max-len 256
# Enable activerehashing for memory efficiency tracking
activerehashing yes
# Memory policy (TigerOps tracks eviction events)
maxmemory-policy allkeys-lru
---
# TigerOps Redis Exporter — docker-compose.yml
services:
tigerops-redis-exporter:
image: atatus/redis-exporter:latest
environment:
REDIS_ADDR: "redis://redis:6379"
REDIS_PASSWORD: "${REDIS_PASSWORD}"
TIGEROPS_ENDPOINT: "https://ingest.atatus.net/api/v1/write"
TIGEROPS_API_KEY: "${TIGEROPS_API_KEY}"
# Scrape all keyspaces
REDIS_EXPORTER_CHECK_KEYS: "db0=*"
ports:
- "9121:9121"
restart: unless-stoppedCommon Questions
Does TigerOps support Redis Cluster and Redis Sentinel?
Yes. TigerOps supports standalone Redis, Redis Cluster (auto-discovering all shards), and Redis Sentinel (monitoring primary/replica roles and failover events). Managed services like ElastiCache, Upstash, and Google Memorystore are also supported.
Can TigerOps detect memory pressure before OOM evictions start?
Yes. TigerOps monitors the maxmemory_usage_ratio and tracks eviction rates as leading indicators. It uses AI forecasting to predict when memory will be exhausted based on key growth rate and TTL distribution.
How do I monitor Redis without exposing metrics publicly?
The TigerOps Redis exporter connects to Redis over an internal network using the standard Redis AUTH command. It does not require any network exposure — you configure it with the Redis host/port/password inside your private network.
Does TigerOps support Valkey (the Redis fork)?
Yes. Valkey is protocol-compatible with Redis, so the TigerOps exporter works without modification. The INFO command output is identical, so all keyspace, memory, and command metrics are collected automatically.
Can I see which application code is causing cache misses?
Yes, if your application uses the TigerOps SDK or OpenTelemetry instrumentation. TigerOps correlates Redis cache miss events with the application trace spans that triggered them, showing exactly which code path has the lowest hit rate.
Full Visibility Into Your Redis Layer
No credit card required. Connect in minutes. Latency, memory, and keyspace metrics immediately.