Azure Redis Cache Integration
Cache hit ratios, memory usage, and connection counts for Azure Cache for Redis. Detect eviction pressure and hit ratio drops before they degrade your application response times.
How It Works
Assign Monitoring Reader Role
Grant the TigerOps Service Principal the Monitoring Reader role on your Azure Cache for Redis resource group. All metrics flow through Azure Monitor with no Redis AUTH password needed.
Enable Diagnostic Settings
Turn on Diagnostic Settings for your Redis cache instance to stream the ConnectedClients, CacheHits, CacheMisses, and UsedMemory metrics to a Log Analytics workspace.
Configure Cache Tracking
Add your Redis cache resource name in TigerOps. The integration automatically discovers all shards for clustered caches and begins tracking hit ratios and memory pressure per shard.
Set Memory & Hit Ratio Alerts
Define memory usage and cache hit ratio thresholds. TigerOps alerts when hit ratios drop below your baseline or memory approaches the eviction threshold, giving you time to scale up.
What You Get Out of the Box
Cache Hit Ratio Tracking
Real-time and historical cache hit and miss rates with per-command breakdown. TigerOps baselines your expected hit ratio and alerts on deviations that signal cache warming issues or key expiry problems.
Memory Usage & Eviction
Used memory percentage, memory RSS, and evicted keys count per instance and per shard. Track memory fragmentation ratio and get warned before maxmemory policy starts dropping keys.
Connection Count Monitoring
Connected client counts, blocked client counts, and connection rejection rates. Detect connection pool exhaustion in your application before it causes Redis timeout errors.
Command Throughput Metrics
Total operations per second, GetCommand and SetCommand rates, and server load percentage. Identify command patterns that saturate the Redis event loop and cause latency spikes.
Keyspace & Expiry Analytics
Key count per database, expired keys rate, and keyspace hits versus misses. Monitor key TTL distribution to ensure your caching strategy is working as designed.
AI Cache Pattern Analysis
TigerOps AI detects cache stampede patterns, unusual miss rate spikes, and memory growth anomalies. Root cause hints point to specific application deployments or traffic changes that triggered the cache degradation.
Enable Redis Cache Diagnostics
Stream Redis metrics to Log Analytics for full cache visibility in TigerOps.
#!/bin/bash
# TigerOps — Azure Cache for Redis integration setup
REDIS_NAME="my-redis-cache"
RESOURCE_GROUP="my-resource-group"
WORKSPACE_ID="/subscriptions/${SUBSCRIPTION_ID}/resourceGroups/${RESOURCE_GROUP}/providers/Microsoft.OperationalInsights/workspaces/tigerops-workspace"
REDIS_RESOURCE="/subscriptions/${SUBSCRIPTION_ID}/resourceGroups/${RESOURCE_GROUP}/providers/Microsoft.Cache/Redis/${REDIS_NAME}"
# Enable diagnostic settings for Redis
az monitor diagnostic-settings create \
--name tigerops-redis \
--resource "${REDIS_RESOURCE}" \
--workspace "${WORKSPACE_ID}" \
--metrics '[
{
"category": "AllMetrics",
"enabled": true,
"retentionPolicy": { "days": 30, "enabled": true }
}
]'
# Key metrics TigerOps will track:
# - CacheHits / CacheMisses (hit ratio)
# - ConnectedClients
# - UsedMemory / UsedMemoryPercentage
# - EvictedKeys
# - TotalCommandsProcessed
# - ServerLoad
# - Errors
echo "Redis Cache diagnostics enabled for: ${REDIS_NAME}"
echo "Metrics will appear in TigerOps within 2 minutes"Common Questions
Does TigerOps support Azure Cache for Redis Cluster tier?
Yes. TigerOps monitors all Azure Cache for Redis tiers: Basic, Standard, Premium, and Enterprise. For clustered Premium and Enterprise caches, metrics are tracked per shard with aggregate views available.
How does TigerOps calculate the cache hit ratio?
TigerOps computes cache hit ratio as CacheHits / (CacheHits + CacheMisses) using the Azure Monitor metrics emitted by the Redis server. The ratio is calculated at 1-minute granularity and trended over time.
Can TigerOps detect Redis evictions before they cause application issues?
Yes. TigerOps tracks the evicted_keys metric and memory usage together. When memory usage exceeds 80% of the configured maxmemory, TigerOps raises a warning alert so you can scale up or adjust TTLs before evictions impact cache hit ratios.
Does TigerOps support geo-replication for Premium Redis caches?
Yes. For Premium tier caches with geo-replication enabled, TigerOps monitors both the primary and replica instances and tracks replication lag between them. Alerts fire when the replica falls behind or becomes disconnected.
How does TigerOps correlate Redis cache degradation with application performance?
When TigerOps detects a cache hit ratio drop or memory eviction spike, it correlates the timing with application traces to identify which services and endpoints are most affected by the cache degradation, helping you prioritize response actions.
Keep Your Redis Cache Performing at Peak Efficiency
Hit ratio tracking, eviction alerts, and AI cache pattern analysis for Azure Cache for Redis. Connect in 5 minutes.