Azure Cache for Redis monitoring data reference

  • Article

This article contains all the monitoring reference information for this service.

See Monitor Azure Cache for Redis for details on the data you can collect for Azure Cache for Redis and how to use it.

Metrics

This section lists all the automatically collected platform metrics for this service. These metrics are also part of the global list of all platform metrics supported in Azure Monitor.

For information on metric retention, see Azure Monitor Metrics overview.

For more details and information about the supported metrics for Microsoft.Cache/redis, see List of metrics.

Supported metrics for Microsoft.Cache/redis

The following table lists the metrics available for the Microsoft.Cache/redis resource type.

Table headings

  • Metric - The metric display name as it appears in the Azure portal.
  • Name in Rest API - Metric name as referred to in the REST API.
  • Unit - Unit of measure.
  • Aggregation - The default aggregation type. Valid values: Average, Minimum, Maximum, Total, Count.
  • Dimensions - Dimensions available for the metric.
  • Time Grains - Intervals at which the metric is sampled. For example, PT1M indicates that the metric is sampled every minute, PT30M every 30 minutes, PT1H every hour, and so on.
  • DS Export- Whether the metric is exportable to Azure Monitor Logs via Diagnostic Settings. For information on exporting metrics, see Create diagnostic settings in Azure Monitor.
Metric Name in REST API Unit Aggregation Dimensions Time Grains DS Export
Cache Hits (Instance Based)

The number of successful key lookups. For more details, see https://aka.ms/redis/metrics.		 allcachehits Count Total ShardId, Port, Primary PT1M Yes
Cache Misses (Instance Based)

The number of failed key lookups. For more details, see https://aka.ms/redis/metrics.		 allcachemisses Count Total ShardId, Port, Primary PT1M Yes
Cache Read (Instance Based)

The amount of data read from the cache in bytes per second. For more details, see https://aka.ms/redis/metrics.		 allcacheRead BytesPerSecond Maximum ShardId, Port, Primary PT1M Yes
Cache Write (Instance Based)

The amount of data written to the cache in bytes per second. For more details, see https://aka.ms/redis/metrics.		 allcacheWrite BytesPerSecond Maximum ShardId, Port, Primary PT1M Yes
Connected Clients (Instance Based)

The number of client connections to the cache. For more details, see https://aka.ms/redis/metrics.		 allconnectedclients Count Maximum ShardId, Port, Primary PT1M Yes
Connections Closed Per Second (Instance Based)

The number of instantaneous connections closed per second on the cache via port 6379 or 6380 (SSL). For more details, see https://aka.ms/redis/metrics.		 allConnectionsClosedPerSecond CountPerSecond Average, Minimum, Maximum, Count ShardId, Primary, Ssl PT1M Yes
Connections Created Per Second (Instance Based)

The number of instantaneous connections created per second on the cache via port 6379 or 6380 (SSL). For more details, see https://aka.ms/redis/metrics.		 allConnectionsCreatedPerSecond CountPerSecond Average, Minimum, Maximum, Count ShardId, Primary, Ssl PT1M Yes
Evicted Keys (Instance Based)

The number of items evicted from the cache. For more details, see https://aka.ms/redis/metrics.		 allevictedkeys Count Total ShardId, Port, Primary PT1M Yes
Expired Keys (Instance Based)

The number of items expired from the cache. For more details, see https://aka.ms/redis/metrics.		 allexpiredkeys Count Total ShardId, Port, Primary PT1M Yes
Gets (Instance Based)

The number of get operations from the cache. For more details, see https://aka.ms/redis/metrics.		 allgetcommands Count Total ShardId, Port, Primary PT1M Yes
Operations Per Second (Instance Based)

The number of instantaneous operations per second executed on the cache. For more details, see https://aka.ms/redis/metrics.		 alloperationsPerSecond Count Maximum ShardId, Port, Primary PT1M Yes
CPU (Instance Based)

The CPU utilization of the Azure Redis Cache server as a percentage. For more details, see https://aka.ms/redis/metrics.		 allpercentprocessortime Percent Maximum ShardId, Port, Primary PT1M Yes
Server Load (Instance Based)

The percentage of cycles in which the Redis server is busy processing and not waiting idle for messages. For more details, see https://aka.ms/redis/metrics.		 allserverLoad Percent Maximum ShardId, Port, Primary PT1M Yes
Sets (Instance Based)

The number of set operations to the cache. For more details, see https://aka.ms/redis/metrics.		 allsetcommands Count Total ShardId, Port, Primary PT1M Yes
Total Operations (Instance Based)

The total number of commands processed by the cache server. For more details, see https://aka.ms/redis/metrics.		 alltotalcommandsprocessed Count Total ShardId, Port, Primary PT1M Yes
Total Keys (Instance Based)

The total number of items in the cache. For more details, see https://aka.ms/redis/metrics.		 alltotalkeys Count Maximum ShardId, Port, Primary PT1M Yes
Used Memory (Instance Based)

The amount of cache memory used for key/value pairs in the cache in MB. For more details, see https://aka.ms/redis/metrics.		 allusedmemory Bytes Maximum ShardId, Port, Primary PT1M Yes
Used Memory Percentage (Instance Based)

The percentage of cache memory used for key/value pairs. For more details, see https://aka.ms/redis/metrics.		 allusedmemorypercentage Percent Maximum ShardId, Port, Primary PT1M Yes
Used Memory RSS (Instance Based)

The amount of cache memory used in MB, including fragmentation and metadata. For more details, see https://aka.ms/redis/metrics.		 allusedmemoryRss Bytes Maximum ShardId, Port, Primary PT1M Yes
Cache Hits

The number of successful key lookups. For more details, see https://aka.ms/redis/metrics.		 cachehits Count Total ShardId PT1M Yes
Cache Hits (Shard 0)

The number of successful key lookups. For more details, see https://aka.ms/redis/metrics.		 cachehits0 Count Total <none> PT1M Yes
Cache Hits (Shard 1)

The number of successful key lookups. For more details, see https://aka.ms/redis/metrics.		 cachehits1 Count Total <none> PT1M Yes
Cache Hits (Shard 2)

The number of successful key lookups. For more details, see https://aka.ms/redis/metrics.		 cachehits2 Count Total <none> PT1M Yes
Cache Hits (Shard 3)

The number of successful key lookups. For more details, see https://aka.ms/redis/metrics.		 cachehits3 Count Total <none> PT1M Yes
Cache Hits (Shard 4)

The number of successful key lookups. For more details, see https://aka.ms/redis/metrics.		 cachehits4 Count Total <none> PT1M Yes
Cache Hits (Shard 5)

The number of successful key lookups. For more details, see https://aka.ms/redis/metrics.		 cachehits5 Count Total <none> PT1M Yes
Cache Hits (Shard 6)

The number of successful key lookups. For more details, see https://aka.ms/redis/metrics.		 cachehits6 Count Total <none> PT1M Yes
Cache Hits (Shard 7)

The number of successful key lookups. For more details, see https://aka.ms/redis/metrics.		 cachehits7 Count Total <none> PT1M Yes
Cache Hits (Shard 8)

The number of successful key lookups. For more details, see https://aka.ms/redis/metrics.		 cachehits8 Count Total <none> PT1M Yes
Cache Hits (Shard 9)

The number of successful key lookups. For more details, see https://aka.ms/redis/metrics.		 cachehits9 Count Total <none> PT1M Yes
Cache Latency Microseconds (Preview)

The latency to the cache in microseconds. For more details, see https://aka.ms/redis/metrics.		 cacheLatency Count Average ShardId PT1M Yes
Cache Misses

The number of failed key lookups. For more details, see https://aka.ms/redis/metrics.		 cachemisses Count Total ShardId PT1M Yes
Cache Misses (Shard 0)

The number of failed key lookups. For more details, see https://aka.ms/redis/metrics.		 cachemisses0 Count Total <none> PT1M Yes
Cache Misses (Shard 1)

The number of failed key lookups. For more details, see https://aka.ms/redis/metrics.		 cachemisses1 Count Total <none> PT1M Yes
Cache Misses (Shard 2)

The number of failed key lookups. For more details, see https://aka.ms/redis/metrics.		 cachemisses2 Count Total <none> PT1M Yes
Cache Misses (Shard 3)

The number of failed key lookups. For more details, see https://aka.ms/redis/metrics.		 cachemisses3 Count Total <none> PT1M Yes
Cache Misses (Shard 4)

The number of failed key lookups. For more details, see https://aka.ms/redis/metrics.		 cachemisses4 Count Total <none> PT1M Yes
Cache Misses (Shard 5)

The number of failed key lookups. For more details, see https://aka.ms/redis/metrics.		 cachemisses5 Count Total <none> PT1M Yes
Cache Misses (Shard 6)

The number of failed key lookups. For more details, see https://aka.ms/redis/metrics.		 cachemisses6 Count Total <none> PT1M Yes
Cache Misses (Shard 7)

The number of failed key lookups. For more details, see https://aka.ms/redis/metrics.		 cachemisses7 Count Total <none> PT1M Yes
Cache Misses (Shard 8)

The number of failed key lookups. For more details, see https://aka.ms/redis/metrics.		 cachemisses8 Count Total <none> PT1M Yes
Cache Misses (Shard 9)

The number of failed key lookups. For more details, see https://aka.ms/redis/metrics.		 cachemisses9 Count Total <none> PT1M Yes
Cache Miss Rate

The % of get requests that miss. For more details, see https://aka.ms/redis/metrics.		 cachemissrate Percent Total ShardId PT1M Yes
Cache Read

The amount of data read from the cache in bytes per second. For more details, see https://aka.ms/redis/metrics.		 cacheRead BytesPerSecond Maximum ShardId PT1M Yes
Cache Read (Shard 0)

The amount of data read from the cache in bytes per second. For more details, see https://aka.ms/redis/metrics.		 cacheRead0 BytesPerSecond Maximum <none> PT1M Yes
Cache Read (Shard 1)

The amount of data read from the cache in bytes per second. For more details, see https://aka.ms/redis/metrics.		 cacheRead1 BytesPerSecond Maximum <none> PT1M Yes
Cache Read (Shard 2)

The amount of data read from the cache in bytes per second. For more details, see https://aka.ms/redis/metrics.		 cacheRead2 BytesPerSecond Maximum <none> PT1M Yes
Cache Read (Shard 3)

The amount of data read from the cache in bytes per second. For more details, see https://aka.ms/redis/metrics.		 cacheRead3 BytesPerSecond Maximum <none> PT1M Yes
Cache Read (Shard 4)

The amount of data read from the cache in bytes per second. For more details, see https://aka.ms/redis/metrics.		 cacheRead4 BytesPerSecond Maximum <none> PT1M Yes
Cache Read (Shard 5)

The amount of data read from the cache in bytes per second. For more details, see https://aka.ms/redis/metrics.		 cacheRead5 BytesPerSecond Maximum <none> PT1M Yes
Cache Read (Shard 6)

The amount of data read from the cache in bytes per second. For more details, see https://aka.ms/redis/metrics.		 cacheRead6 BytesPerSecond Maximum <none> PT1M Yes
Cache Read (Shard 7)

The amount of data read from the cache in bytes per second. For more details, see https://aka.ms/redis/metrics.		 cacheRead7 BytesPerSecond Maximum <none> PT1M Yes
Cache Read (Shard 8)

The amount of data read from the cache in bytes per second. For more details, see https://aka.ms/redis/metrics.		 cacheRead8 BytesPerSecond Maximum <none> PT1M Yes
Cache Read (Shard 9)

The amount of data read from the cache in bytes per second. For more details, see https://aka.ms/redis/metrics.		 cacheRead9 BytesPerSecond Maximum <none> PT1M Yes
Cache Write

The amount of data written to the cache in bytes per second. For more details, see https://aka.ms/redis/metrics.		 cacheWrite BytesPerSecond Maximum ShardId PT1M Yes
Cache Write (Shard 0)

The amount of data written to the cache in bytes per second. For more details, see https://aka.ms/redis/metrics.		 cacheWrite0 BytesPerSecond Maximum <none> PT1M Yes
Cache Write (Shard 1)

The amount of data written to the cache in bytes per second. For more details, see https://aka.ms/redis/metrics.		 cacheWrite1 BytesPerSecond Maximum <none> PT1M Yes
Cache Write (Shard 2)

The amount of data written to the cache in bytes per second. For more details, see https://aka.ms/redis/metrics.		 cacheWrite2 BytesPerSecond Maximum <none> PT1M Yes
Cache Write (Shard 3)

The amount of data written to the cache in bytes per second. For more details, see https://aka.ms/redis/metrics.		 cacheWrite3 BytesPerSecond Maximum <none> PT1M Yes
Cache Write (Shard 4)

The amount of data written to the cache in bytes per second. For more details, see https://aka.ms/redis/metrics.		 cacheWrite4 BytesPerSecond Maximum <none> PT1M Yes
Cache Write (Shard 5)

The amount of data written to the cache in bytes per second. For more details, see https://aka.ms/redis/metrics.		 cacheWrite5 BytesPerSecond Maximum <none> PT1M Yes
Cache Write (Shard 6)

The amount of data written to the cache in bytes per second. For more details, see https://aka.ms/redis/metrics.		 cacheWrite6 BytesPerSecond Maximum <none> PT1M Yes
Cache Write (Shard 7)

The amount of data written to the cache in bytes per second. For more details, see https://aka.ms/redis/metrics.		 cacheWrite7 BytesPerSecond Maximum <none> PT1M Yes
Cache Write (Shard 8)

The amount of data written to the cache in bytes per second. For more details, see https://aka.ms/redis/metrics.		 cacheWrite8 BytesPerSecond Maximum <none> PT1M Yes
Cache Write (Shard 9)

The amount of data written to the cache in bytes per second. For more details, see https://aka.ms/redis/metrics.		 cacheWrite9 BytesPerSecond Maximum <none> PT1M Yes
Connected Clients

The number of client connections to the cache. For more details, see https://aka.ms/redis/metrics.		 connectedclients Count Maximum ShardId PT1M Yes
Connected Clients (Shard 0)

The number of client connections to the cache. For more details, see https://aka.ms/redis/metrics.		 connectedclients0 Count Maximum <none> PT1M Yes
Connected Clients (Shard 1)

The number of client connections to the cache. For more details, see https://aka.ms/redis/metrics.		 connectedclients1 Count Maximum <none> PT1M Yes
Connected Clients (Shard 2)

The number of client connections to the cache. For more details, see https://aka.ms/redis/metrics.		 connectedclients2 Count Maximum <none> PT1M Yes
Connected Clients (Shard 3)

The number of client connections to the cache. For more details, see https://aka.ms/redis/metrics.		 connectedclients3 Count Maximum <none> PT1M Yes
Connected Clients (Shard 4)

The number of client connections to the cache. For more details, see https://aka.ms/redis/metrics.		 connectedclients4 Count Maximum <none> PT1M Yes
Connected Clients (Shard 5)

The number of client connections to the cache. For more details, see https://aka.ms/redis/metrics.		 connectedclients5 Count Maximum <none> PT1M Yes
Connected Clients (Shard 6)

The number of client connections to the cache. For more details, see https://aka.ms/redis/metrics.		 connectedclients6 Count Maximum <none> PT1M Yes
Connected Clients (Shard 7)

The number of client connections to the cache. For more details, see https://aka.ms/redis/metrics.		 connectedclients7 Count Maximum <none> PT1M Yes
Connected Clients (Shard 8)

The number of client connections to the cache. For more details, see https://aka.ms/redis/metrics.		 connectedclients8 Count Maximum <none> PT1M Yes
Connected Clients (Shard 9)

The number of client connections to the cache. For more details, see https://aka.ms/redis/metrics.		 connectedclients9 Count Maximum <none> PT1M Yes
Connected Clients using Microsoft Entra Token (Instance Based)

The number of client connections to the cache using Microsoft Entra Token. For more details, see https://aka.ms/redis/metrics.		 ConnectedClientsUsingAADToken Count Maximum ShardId, Port, Primary PT1M Yes
Errors

The number errors that occured on the cache. For more details, see https://aka.ms/redis/metrics.		 errors Count Maximum ShardId, ErrorType PT1M Yes
Evicted Keys

The number of items evicted from the cache. For more details, see https://aka.ms/redis/metrics.		 evictedkeys Count Total ShardId PT1M Yes
Evicted Keys (Shard 0)

The number of items evicted from the cache. For more details, see https://aka.ms/redis/metrics.		 evictedkeys0 Count Total <none> PT1M Yes
Evicted Keys (Shard 1)

The number of items evicted from the cache. For more details, see https://aka.ms/redis/metrics.		 evictedkeys1 Count Total <none> PT1M Yes
Evicted Keys (Shard 2)

The number of items evicted from the cache. For more details, see https://aka.ms/redis/metrics.		 evictedkeys2 Count Total <none> PT1M Yes
Evicted Keys (Shard 3)

The number of items evicted from the cache. For more details, see https://aka.ms/redis/metrics.		 evictedkeys3 Count Total <none> PT1M Yes
Evicted Keys (Shard 4)

The number of items evicted from the cache. For more details, see https://aka.ms/redis/metrics.		 evictedkeys4 Count Total <none> PT1M Yes
Evicted Keys (Shard 5)

The number of items evicted from the cache. For more details, see https://aka.ms/redis/metrics.		 evictedkeys5 Count Total <none> PT1M Yes
Evicted Keys (Shard 6)

The number of items evicted from the cache. For more details, see https://aka.ms/redis/metrics.		 evictedkeys6 Count Total <none> PT1M Yes
Evicted Keys (Shard 7)

The number of items evicted from the cache. For more details, see https://aka.ms/redis/metrics.		 evictedkeys7 Count Total <none> PT1M Yes
Evicted Keys (Shard 8)

The number of items evicted from the cache. For more details, see https://aka.ms/redis/metrics.		 evictedkeys8 Count Total <none> PT1M Yes
Evicted Keys (Shard 9)

The number of items evicted from the cache. For more details, see https://aka.ms/redis/metrics.		 evictedkeys9 Count Total <none> PT1M Yes
Expired Keys

The number of items expired from the cache. For more details, see https://aka.ms/redis/metrics.		 expiredkeys Count Total ShardId PT1M Yes
Expired Keys (Shard 0)

The number of items expired from the cache. For more details, see https://aka.ms/redis/metrics.		 expiredkeys0 Count Total <none> PT1M Yes
Expired Keys (Shard 1)

The number of items expired from the cache. For more details, see https://aka.ms/redis/metrics.		 expiredkeys1 Count Total <none> PT1M Yes
Expired Keys (Shard 2)

The number of items expired from the cache. For more details, see https://aka.ms/redis/metrics.		 expiredkeys2 Count Total <none> PT1M Yes
Expired Keys (Shard 3)

The number of items expired from the cache. For more details, see https://aka.ms/redis/metrics.		 expiredkeys3 Count Total <none> PT1M Yes
Expired Keys (Shard 4)

The number of items expired from the cache. For more details, see https://aka.ms/redis/metrics.		 expiredkeys4 Count Total <none> PT1M Yes
Expired Keys (Shard 5)

The number of items expired from the cache. For more details, see https://aka.ms/redis/metrics.		 expiredkeys5 Count Total <none> PT1M Yes
Expired Keys (Shard 6)

The number of items expired from the cache. For more details, see https://aka.ms/redis/metrics.		 expiredkeys6 Count Total <none> PT1M Yes
Expired Keys (Shard 7)

The number of items expired from the cache. For more details, see https://aka.ms/redis/metrics.		 expiredkeys7 Count Total <none> PT1M Yes
Expired Keys (Shard 8)

The number of items expired from the cache. For more details, see https://aka.ms/redis/metrics.		 expiredkeys8 Count Total <none> PT1M Yes
Expired Keys (Shard 9)

The number of items expired from the cache. For more details, see https://aka.ms/redis/metrics.		 expiredkeys9 Count Total <none> PT1M Yes
Geo-replication Connectivity Lag

Time in seconds since last successful data synchronization with geo-primary cache. Value will continue to increase if the link status is down. For more details, see https://aka.ms/redis/georeplicationmetrics.		 GeoReplicationConnectivityLag Seconds Average, Minimum, Maximum ShardId PT1M Yes
Geo-replication Data Sync Offset

Approximate amount of data in bytes that needs to be synchronized to geo-secondary cache. For more details, see https://aka.ms/redis/georeplicationmetrics.		 GeoReplicationDataSyncOffset Bytes Average, Minimum, Maximum ShardId PT1M Yes
Geo-replication Full Sync Event Finished

Fired on completion of a full synchronization event between geo-replicated caches. This metric reports 0 most of the time because geo-replication uses partial resynchronizations for any new data added after the initial full synchronization. For more details, see https://aka.ms/redis/georeplicationmetrics.		 GeoReplicationFullSyncEventFinished Count Count ShardId PT1M Yes
Geo-replication Full Sync Event Started

Fired on initiation of a full synchronization event between geo-replicated caches. This metric reports 0 most of the time because geo-replication uses partial resynchronizations for any new data added after the initial full synchronization. For more details, see https://aka.ms/redis/georeplicationmetrics.		 GeoReplicationFullSyncEventStarted Count Count ShardId PT1M Yes
Geo-replication Healthy

The health status of geo-replication link. 1 if healthy and 0 if disconnected or unhealthy. For more details, see https://aka.ms/redis/georeplicationmetrics.		 GeoReplicationHealthy Count Average, Minimum, Maximum ShardId PT1M Yes
Gets

The number of get operations from the cache. For more details, see https://aka.ms/redis/metrics.		 getcommands Count Total ShardId PT1M Yes
Gets (Shard 0)

The number of get operations from the cache. For more details, see https://aka.ms/redis/metrics.		 getcommands0 Count Total <none> PT1M Yes
Gets (Shard 1)

The number of get operations from the cache. For more details, see https://aka.ms/redis/metrics.		 getcommands1 Count Total <none> PT1M Yes
Gets (Shard 2)

The number of get operations from the cache. For more details, see https://aka.ms/redis/metrics.		 getcommands2 Count Total <none> PT1M Yes
Gets (Shard 3)

The number of get operations from the cache. For more details, see https://aka.ms/redis/metrics.		 getcommands3 Count Total <none> PT1M Yes
Gets (Shard 4)

The number of get operations from the cache. For more details, see https://aka.ms/redis/metrics.		 getcommands4 Count Total <none> PT1M Yes
Gets (Shard 5)

The number of get operations from the cache. For more details, see https://aka.ms/redis/metrics.		 getcommands5 Count Total <none> PT1M Yes
Gets (Shard 6)

The number of get operations from the cache. For more details, see https://aka.ms/redis/metrics.		 getcommands6 Count Total <none> PT1M Yes
Gets (Shard 7)

The number of get operations from the cache. For more details, see https://aka.ms/redis/metrics.		 getcommands7 Count Total <none> PT1M Yes
Gets (Shard 8)

The number of get operations from the cache. For more details, see https://aka.ms/redis/metrics.		 getcommands8 Count Total <none> PT1M Yes
Gets (Shard 9)

The number of get operations from the cache. For more details, see https://aka.ms/redis/metrics.		 getcommands9 Count Total <none> PT1M Yes
99th percentile latency

Measures the worst-case (99th percentile) latency of server-side commands in microseconds. Measured by issuing PING commands from the load balancer to the Redis server and tracking the time to respond.		 LatencyP99 Count Average, Minimum, Maximum <none> PT1M Yes
Operations Per Second

The number of instantaneous operations per second executed on the cache. For more details, see https://aka.ms/redis/metrics.		 operationsPerSecond Count Maximum ShardId PT1M Yes
Operations Per Second (Shard 0)

The number of instantaneous operations per second executed on the cache. For more details, see https://aka.ms/redis/metrics.		 operationsPerSecond0 Count Maximum <none> PT1M Yes
Operations Per Second (Shard 1)

The number of instantaneous operations per second executed on the cache. For more details, see https://aka.ms/redis/metrics.		 operationsPerSecond1 Count Maximum <none> PT1M Yes
Operations Per Second (Shard 2)

The number of instantaneous operations per second executed on the cache. For more details, see https://aka.ms/redis/metrics.		 operationsPerSecond2 Count Maximum <none> PT1M Yes
Operations Per Second (Shard 3)

The number of instantaneous operations per second executed on the cache. For more details, see https://aka.ms/redis/metrics.		 operationsPerSecond3 Count Maximum <none> PT1M Yes
Operations Per Second (Shard 4)

The number of instantaneous operations per second executed on the cache. For more details, see https://aka.ms/redis/metrics.		 operationsPerSecond4 Count Maximum <none> PT1M Yes
Operations Per Second (Shard 5)

The number of instantaneous operations per second executed on the cache. For more details, see https://aka.ms/redis/metrics.		 operationsPerSecond5 Count Maximum <none> PT1M Yes
Operations Per Second (Shard 6)

The number of instantaneous operations per second executed on the cache. For more details, see https://aka.ms/redis/metrics.		 operationsPerSecond6 Count Maximum <none> PT1M Yes
Operations Per Second (Shard 7)

The number of instantaneous operations per second executed on the cache. For more details, see https://aka.ms/redis/metrics.		 operationsPerSecond7 Count Maximum <none> PT1M Yes
Operations Per Second (Shard 8)

The number of instantaneous operations per second executed on the cache. For more details, see https://aka.ms/redis/metrics.		 operationsPerSecond8 Count Maximum <none> PT1M Yes
Operations Per Second (Shard 9)

The number of instantaneous operations per second executed on the cache. For more details, see https://aka.ms/redis/metrics.		 operationsPerSecond9 Count Maximum <none> PT1M Yes
CPU

The CPU utilization of the Azure Redis Cache server as a percentage. For more details, see https://aka.ms/redis/metrics.		 percentProcessorTime Percent Maximum ShardId PT1M Yes
CPU (Shard 0)

The CPU utilization of the Azure Redis Cache server as a percentage. For more details, see https://aka.ms/redis/metrics.		 percentProcessorTime0 Percent Maximum <none> PT1M Yes
CPU (Shard 1)

The CPU utilization of the Azure Redis Cache server as a percentage. For more details, see https://aka.ms/redis/metrics.		 percentProcessorTime1 Percent Maximum <none> PT1M Yes
CPU (Shard 2)

The CPU utilization of the Azure Redis Cache server as a percentage. For more details, see https://aka.ms/redis/metrics.		 percentProcessorTime2 Percent Maximum <none> PT1M Yes
CPU (Shard 3)

The CPU utilization of the Azure Redis Cache server as a percentage. For more details, see https://aka.ms/redis/metrics.		 percentProcessorTime3 Percent Maximum <none> PT1M Yes
CPU (Shard 4)

The CPU utilization of the Azure Redis Cache server as a percentage. For more details, see https://aka.ms/redis/metrics.		 percentProcessorTime4 Percent Maximum <none> PT1M Yes
CPU (Shard 5)

The CPU utilization of the Azure Redis Cache server as a percentage. For more details, see https://aka.ms/redis/metrics.		 percentProcessorTime5 Percent Maximum <none> PT1M Yes
CPU (Shard 6)

The CPU utilization of the Azure Redis Cache server as a percentage. For more details, see https://aka.ms/redis/metrics.		 percentProcessorTime6 Percent Maximum <none> PT1M Yes
CPU (Shard 7)

The CPU utilization of the Azure Redis Cache server as a percentage. For more details, see https://aka.ms/redis/metrics.		 percentProcessorTime7 Percent Maximum <none> PT1M Yes
CPU (Shard 8)

The CPU utilization of the Azure Redis Cache server as a percentage. For more details, see https://aka.ms/redis/metrics.		 percentProcessorTime8 Percent Maximum <none> PT1M Yes
CPU (Shard 9)

The CPU utilization of the Azure Redis Cache server as a percentage. For more details, see https://aka.ms/redis/metrics.		 percentProcessorTime9 Percent Maximum <none> PT1M Yes
Server Load

The percentage of cycles in which the Redis server is busy processing and not waiting idle for messages. For more details, see https://aka.ms/redis/metrics.		 serverLoad Percent Maximum ShardId PT1M Yes
Server Load (Shard 0)

The percentage of cycles in which the Redis server is busy processing and not waiting idle for messages. For more details, see https://aka.ms/redis/metrics.		 serverLoad0 Percent Maximum <none> PT1M Yes
Server Load (Shard 1)

The percentage of cycles in which the Redis server is busy processing and not waiting idle for messages. For more details, see https://aka.ms/redis/metrics.		 serverLoad1 Percent Maximum <none> PT1M Yes
Server Load (Shard 2)

The percentage of cycles in which the Redis server is busy processing and not waiting idle for messages. For more details, see https://aka.ms/redis/metrics.		 serverLoad2 Percent Maximum <none> PT1M Yes
Server Load (Shard 3)

The percentage of cycles in which the Redis server is busy processing and not waiting idle for messages. For more details, see https://aka.ms/redis/metrics.		 serverLoad3 Percent Maximum <none> PT1M Yes
Server Load (Shard 4)

The percentage of cycles in which the Redis server is busy processing and not waiting idle for messages. For more details, see https://aka.ms/redis/metrics.		 serverLoad4 Percent Maximum <none> PT1M Yes
Server Load (Shard 5)

The percentage of cycles in which the Redis server is busy processing and not waiting idle for messages. For more details, see https://aka.ms/redis/metrics.		 serverLoad5 Percent Maximum <none> PT1M Yes
Server Load (Shard 6)

The percentage of cycles in which the Redis server is busy processing and not waiting idle for messages. For more details, see https://aka.ms/redis/metrics.		 serverLoad6 Percent Maximum <none> PT1M Yes
Server Load (Shard 7)

The percentage of cycles in which the Redis server is busy processing and not waiting idle for messages. For more details, see https://aka.ms/redis/metrics.		 serverLoad7 Percent Maximum <none> PT1M Yes
Server Load (Shard 8)

The percentage of cycles in which the Redis server is busy processing and not waiting idle for messages. For more details, see https://aka.ms/redis/metrics.		 serverLoad8 Percent Maximum <none> PT1M Yes
Server Load (Shard 9)

The percentage of cycles in which the Redis server is busy processing and not waiting idle for messages. For more details, see https://aka.ms/redis/metrics.		 serverLoad9 Percent Maximum <none> PT1M Yes
Sets

The number of set operations to the cache. For more details, see https://aka.ms/redis/metrics.		 setcommands Count Total ShardId PT1M Yes
Sets (Shard 0)

The number of set operations to the cache. For more details, see https://aka.ms/redis/metrics.		 setcommands0 Count Total <none> PT1M Yes
Sets (Shard 1)

The number of set operations to the cache. For more details, see https://aka.ms/redis/metrics.		 setcommands1 Count Total <none> PT1M Yes
Sets (Shard 2)

The number of set operations to the cache. For more details, see https://aka.ms/redis/metrics.		 setcommands2 Count Total <none> PT1M Yes
Sets (Shard 3)

The number of set operations to the cache. For more details, see https://aka.ms/redis/metrics.		 setcommands3 Count Total <none> PT1M Yes
Sets (Shard 4)

The number of set operations to the cache. For more details, see https://aka.ms/redis/metrics.		 setcommands4 Count Total <none> PT1M Yes
Sets (Shard 5)

The number of set operations to the cache. For more details, see https://aka.ms/redis/metrics.		 setcommands5 Count Total <none> PT1M Yes
Sets (Shard 6)

The number of set operations to the cache. For more details, see https://aka.ms/redis/metrics.		 setcommands6 Count Total <none> PT1M Yes
Sets (Shard 7)

The number of set operations to the cache. For more details, see https://aka.ms/redis/metrics.		 setcommands7 Count Total <none> PT1M Yes
Sets (Shard 8)

The number of set operations to the cache. For more details, see https://aka.ms/redis/metrics.		 setcommands8 Count Total <none> PT1M Yes
Sets (Shard 9)

The number of set operations to the cache. For more details, see https://aka.ms/redis/metrics.		 setcommands9 Count Total <none> PT1M Yes
Total Operations

The total number of commands processed by the cache server. For more details, see https://aka.ms/redis/metrics.		 totalcommandsprocessed Count Total ShardId PT1M Yes
Total Operations (Shard 0)

The total number of commands processed by the cache server. For more details, see https://aka.ms/redis/metrics.		 totalcommandsprocessed0 Count Total <none> PT1M Yes
Total Operations (Shard 1)

The total number of commands processed by the cache server. For more details, see https://aka.ms/redis/metrics.		 totalcommandsprocessed1 Count Total <none> PT1M Yes
Total Operations (Shard 2)

The total number of commands processed by the cache server. For more details, see https://aka.ms/redis/metrics.		 totalcommandsprocessed2 Count Total <none> PT1M Yes
Total Operations (Shard 3)

The total number of commands processed by the cache server. For more details, see https://aka.ms/redis/metrics.		 totalcommandsprocessed3 Count Total <none> PT1M Yes
Total Operations (Shard 4)

The total number of commands processed by the cache server. For more details, see https://aka.ms/redis/metrics.		 totalcommandsprocessed4 Count Total <none> PT1M Yes
Total Operations (Shard 5)

The total number of commands processed by the cache server. For more details, see https://aka.ms/redis/metrics.		 totalcommandsprocessed5 Count Total <none> PT1M Yes
Total Operations (Shard 6)

The total number of commands processed by the cache server. For more details, see https://aka.ms/redis/metrics.		 totalcommandsprocessed6 Count Total <none> PT1M Yes
Total Operations (Shard 7)

The total number of commands processed by the cache server. For more details, see https://aka.ms/redis/metrics.		 totalcommandsprocessed7 Count Total <none> PT1M Yes
Total Operations (Shard 8)

The total number of commands processed by the cache server. For more details, see https://aka.ms/redis/metrics.		 totalcommandsprocessed8 Count Total <none> PT1M Yes
Total Operations (Shard 9)

The total number of commands processed by the cache server. For more details, see https://aka.ms/redis/metrics.		 totalcommandsprocessed9 Count Total <none> PT1M Yes
Total Keys

The total number of items in the cache. For more details, see https://aka.ms/redis/metrics.		 totalkeys Count Maximum ShardId PT1M Yes
Total Keys (Shard 0)

The total number of items in the cache. For more details, see https://aka.ms/redis/metrics.		 totalkeys0 Count Maximum <none> PT1M Yes
Total Keys (Shard 1)

The total number of items in the cache. For more details, see https://aka.ms/redis/metrics.		 totalkeys1 Count Maximum <none> PT1M Yes
Total Keys (Shard 2)

The total number of items in the cache. For more details, see https://aka.ms/redis/metrics.		 totalkeys2 Count Maximum <none> PT1M Yes
Total Keys (Shard 3)

The total number of items in the cache. For more details, see https://aka.ms/redis/metrics.		 totalkeys3 Count Maximum <none> PT1M Yes
Total Keys (Shard 4)

The total number of items in the cache. For more details, see https://aka.ms/redis/metrics.		 totalkeys4 Count Maximum <none> PT1M Yes
Total Keys (Shard 5)

The total number of items in the cache. For more details, see https://aka.ms/redis/metrics.		 totalkeys5 Count Maximum <none> PT1M Yes
Total Keys (Shard 6)

The total number of items in the cache. For more details, see https://aka.ms/redis/metrics.		 totalkeys6 Count Maximum <none> PT1M Yes
Total Keys (Shard 7)

The total number of items in the cache. For more details, see https://aka.ms/redis/metrics.		 totalkeys7 Count Maximum <none> PT1M Yes
Total Keys (Shard 8)

The total number of items in the cache. For more details, see https://aka.ms/redis/metrics.		 totalkeys8 Count Maximum <none> PT1M Yes
Total Keys (Shard 9)

The total number of items in the cache. For more details, see https://aka.ms/redis/metrics.		 totalkeys9 Count Maximum <none> PT1M Yes
Used Memory

The amount of cache memory used for key/value pairs in the cache in MB. For more details, see https://aka.ms/redis/metrics.		 usedmemory Bytes Maximum ShardId PT1M Yes
Used Memory (Shard 0)

The amount of cache memory used for key/value pairs in the cache in MB. For more details, see https://aka.ms/redis/metrics.		 usedmemory0 Bytes Maximum <none> PT1M Yes
Used Memory (Shard 1)

The amount of cache memory used for key/value pairs in the cache in MB. For more details, see https://aka.ms/redis/metrics.		 usedmemory1 Bytes Maximum <none> PT1M Yes
Used Memory (Shard 2)

The amount of cache memory used for key/value pairs in the cache in MB. For more details, see https://aka.ms/redis/metrics.		 usedmemory2 Bytes Maximum <none> PT1M Yes
Used Memory (Shard 3)

The amount of cache memory used for key/value pairs in the cache in MB. For more details, see https://aka.ms/redis/metrics.		 usedmemory3 Bytes Maximum <none> PT1M Yes
Used Memory (Shard 4)

The amount of cache memory used for key/value pairs in the cache in MB. For more details, see https://aka.ms/redis/metrics.		 usedmemory4 Bytes Maximum <none> PT1M Yes
Used Memory (Shard 5)

The amount of cache memory used for key/value pairs in the cache in MB. For more details, see https://aka.ms/redis/metrics.		 usedmemory5 Bytes Maximum <none> PT1M Yes
Used Memory (Shard 6)

The amount of cache memory used for key/value pairs in the cache in MB. For more details, see https://aka.ms/redis/metrics.		 usedmemory6 Bytes Maximum <none> PT1M Yes
Used Memory (Shard 7)

The amount of cache memory used for key/value pairs in the cache in MB. For more details, see https://aka.ms/redis/metrics.		 usedmemory7 Bytes Maximum <none> PT1M Yes
Used Memory (Shard 8)

The amount of cache memory used for key/value pairs in the cache in MB. For more details, see https://aka.ms/redis/metrics.		 usedmemory8 Bytes Maximum <none> PT1M Yes
Used Memory (Shard 9)

The amount of cache memory used for key/value pairs in the cache in MB. For more details, see https://aka.ms/redis/metrics.		 usedmemory9 Bytes Maximum <none> PT1M Yes
Used Memory Percentage

The percentage of cache memory used for key/value pairs. For more details, see https://aka.ms/redis/metrics.		 usedmemorypercentage Percent Maximum ShardId PT1M Yes
Used Memory RSS

The amount of cache memory used in MB, including fragmentation and metadata. For more details, see https://aka.ms/redis/metrics.		 usedmemoryRss Bytes Maximum ShardId PT1M Yes
Used Memory RSS (Shard 0)

The amount of cache memory used in MB, including fragmentation and metadata. For more details, see https://aka.ms/redis/metrics.		 usedmemoryRss0 Bytes Maximum <none> PT1M Yes
Used Memory RSS (Shard 1)

The amount of cache memory used in MB, including fragmentation and metadata. For more details, see https://aka.ms/redis/metrics.		 usedmemoryRss1 Bytes Maximum <none> PT1M Yes
Used Memory RSS (Shard 2)

The amount of cache memory used in MB, including fragmentation and metadata. For more details, see https://aka.ms/redis/metrics.		 usedmemoryRss2 Bytes Maximum <none> PT1M Yes
Used Memory RSS (Shard 3)

The amount of cache memory used in MB, including fragmentation and metadata. For more details, see https://aka.ms/redis/metrics.		 usedmemoryRss3 Bytes Maximum <none> PT1M Yes
Used Memory RSS (Shard 4)

The amount of cache memory used in MB, including fragmentation and metadata. For more details, see https://aka.ms/redis/metrics.		 usedmemoryRss4 Bytes Maximum <none> PT1M Yes
Used Memory RSS (Shard 5)

The amount of cache memory used in MB, including fragmentation and metadata. For more details, see https://aka.ms/redis/metrics.		 usedmemoryRss5 Bytes Maximum <none> PT1M Yes
Used Memory RSS (Shard 6)

The amount of cache memory used in MB, including fragmentation and metadata. For more details, see https://aka.ms/redis/metrics.		 usedmemoryRss6 Bytes Maximum <none> PT1M Yes
Used Memory RSS (Shard 7)

The amount of cache memory used in MB, including fragmentation and metadata. For more details, see https://aka.ms/redis/metrics.		 usedmemoryRss7 Bytes Maximum <none> PT1M Yes
Used Memory RSS (Shard 8)

The amount of cache memory used in MB, including fragmentation and metadata. For more details, see https://aka.ms/redis/metrics.		 usedmemoryRss8 Bytes Maximum <none> PT1M Yes
Used Memory RSS (Shard 9)

The amount of cache memory used in MB, including fragmentation and metadata. For more details, see https://aka.ms/redis/metrics.		 usedmemoryRss9 Bytes Maximum <none> PT1M Yes

Azure Cache for Redis metrics

The following list provides details and more information about the supported Azure Monitor metrics for Microsoft.Cache/redis.

  • 99th Percentile Latency (preview)

    • Depicts the worst-case (99th percentile) latency of server-side commands. Measured by issuing PING commands from the load balancer to the Redis server and tracking the time to respond.
    • Useful for tracking the health of your Redis instance. Latency increases if the cache is under heavy load or if there are long running commands that delay the execution of the PING command.
    • This metric is only available in Standard and Premium tier caches.
    • This metric is not available for caches that are affected by Cloud Service retirement. See more information here

  • Cache Latency (preview)

    • The latency of the cache calculated using the internode latency of the cache. This metric is measured in microseconds, and has three dimensions: Avg, Min, and Max. The dimensions represent the average, minimum, and maximum latency of the cache during the specified reporting interval.

  • Cache Misses

    • The number of failed key lookups during the specified reporting interval. This number maps to keyspace_misses from the Redis INFO command. Cache misses don't necessarily mean there's an issue with the cache. For example, when using the cache-aside programming pattern, an application looks first in the cache for an item. If the item isn't there (cache miss), the item is retrieved from the database and added to the cache for next time. Cache misses are normal behavior for the cache-aside programming pattern. If the number of cache misses is higher than expected, examine the application logic that populates and reads from the cache. If items are being evicted from the cache because of memory pressure, then there might be some cache misses, but a better metric to monitor for memory pressure would be Used Memory or Evicted Keys.

  • Cache Miss Rate

    • The percent of unsuccessful key lookups during the specified reporting interval.

  • Cache Read

    • The amount of data read from the cache in Megabytes per second (MB/s) during the specified reporting interval. This value is derived from the network interface cards that support the virtual machine that hosts the cache and isn't Redis specific. This value corresponds to the network bandwidth used by this cache. If you want to set up alerts for server-side network bandwidth limits, then create it using this Cache Read counter. See this table for the observed bandwidth limits for various cache pricing tiers and sizes.

  • Cache Write

    • The amount of data written to the cache in Megabytes per second (MB/s) during the specified reporting interval. This value is derived from the network interface cards that support the virtual machine that hosts the cache and isn't Redis specific. This value corresponds to the network bandwidth of data sent to the cache from the client.

  • Connected Clients

    • The number of client connections to the cache during the specified reporting interval. This number maps to connected_clients from the Redis INFO command. Once the connection limit is reached, later attempts to connect to the cache fail. Even if there are no active client applications, there might still be a few instances of connected clients because of internal processes and connections.

  • Connected Clients Using Microsoft Entra Token (preview)

    • The number of client connections to the cache authenticated using Microsoft Entra token during the specified reporting interval.

  • Connections Created Per Second

    • The number of instantaneous connections created per second on the cache via port 6379 or 6380 (SSL). This metric can help identify whether clients are frequently disconnecting and reconnecting, which can cause higher CPU usage and Redis Server Load.

  • Connections Closed Per Second

    • The number of instantaneous connections closed per second on the cache via port 6379 or 6380 (SSL). This metric can help identify whether clients are frequently disconnecting and reconnecting, which can cause higher CPU usage and Redis Server Load.

  • CPU

    • The CPU utilization of the Azure Cache for Redis server as a percentage during the specified reporting interval. This value maps to the operating system \Processor(_Total)\% Processor Time performance counter. Note that this metric can be noisy due to low priority background security processes running on the node, so we recommend monitoring Server Load metric to track load on a Redis server.

  • Errors

    • Specific failures and performance issues that the cache could be experiencing during a specified reporting interval. This metric has eight dimensions representing different error types. The error types represented now are as follows:
      • Failover - when a cache fails over (subordinate promotes to primary)
      • Dataloss - when there's data loss on the cache
      • UnresponsiveClients - when the clients aren't reading data from the server fast enough, and specifically, when the number of bytes in the Redis server output buffer for a client goes over 1,000,000 bytes
      • AOF - when there's an issue related to AOF persistence
      • RDB - when there's an issue related to RDB persistence
      • Import - when there's an issue related to Import RDB
      • Export - when there's an issue related to Export RDB
      • AADAuthenticationFailure (preview) - when there's an authentication failure using Microsoft Entra access token
      • AADTokenExpired (preview) - when a Microsoft Entra access token used for authentication isn't renewed and it expires.

  • Evicted Keys

    • The number of items evicted from the cache during the specified reporting interval because of the maxmemory limit.
    • This number maps to evicted_keys from the Redis INFO command.

  • Expired Keys

    • The number of items expired from the cache during the specified reporting interval. This value maps to expired_keys from the Redis INFO command.

  • Geo-replication metrics

    Geo-replication metrics are affected by monthly internal maintenance operations. The Azure Cache for Redis service periodically patches all caches with the latest platform features and improvements. During these updates, each cache node is taken offline, which temporarily disables the geo-replication link. If your geo replication link is unhealthy, check to see if it was caused by a patching event on either the geo-primary or geo-secondary cache by using Diagnose and Solve Problems from the Resource menu in the portal. Depending on the amount of data in the cache, the downtime from patching can take anywhere from a few minutes to an hour. If the geo-replication link is unhealthy for over an hour, file a support request.

    The Geo-Replication Dashboard workbook is a simple and easy way to view all Premium-tier geo-replication metrics in the same place. This dashboard pulls together metrics that are only emitted by the geo-primary or geo-secondary, so they can be viewed simultaneously.

    • Geo Replication Connectivity Lag

      • Depicts the time, in seconds, since the last successful data synchronization between geo-primary & geo-secondary. If the link goes down, this value continues to increase, indicating a problem.
      • This metric is only emitted from the geo-secondary cache instance. On the geo-primary instance, this metric has no value.
      • This metric is only available in the Premium tier for caches with geo-replication enabled.

    • Geo Replication Data Sync Offset

      • Depicts the approximate amount of data in bytes that has yet to be synchronized to geo-secondary cache.
      • This metric is only emitted from the geo-primary cache instance. On the geo-secondary instance, this metric has no value.
      • This metric is only available in the Premium tier for caches with geo-replication enabled.

    • Geo Replication Full Sync Event Finished

      • Depicts the completion of full synchronization between geo-replicated caches. When you see lots of writes on geo-primary, and replication between the two caches can’t keep up, then a full sync is needed. A full sync involves copying the complete data from geo-primary to geo-secondary by taking an RDB snapshot rather than a partial sync that occurs on normal instances. See this page for a more detailed explanation.
      • The metric reports zero most of the time because geo-replication uses partial resynchronizations for any new data added after the initial full synchronization.
      • This metric is only emitted from the geo-secondary cache instance. On the geo-primary instance, this metric has no value.
      • This metric is only available in the Premium tier for caches with geo-replication enabled.

    • Geo Replication Full Sync Event Started

      • Depicts the start of full synchronization between geo-replicated caches. When there are many writes in geo-primary, and replication between the two caches can’t keep up, then a full sync is needed. A full sync involves copying the complete data from geo-primary to geo-secondary by taking an RDB snapshot rather than a partial sync that occurs on normal instances. See this page for a more detailed explanation.
      • The metric reports zero most of the time because geo-replication uses partial resynchronizations for any new data added after the initial full synchronization.
      • The metric is only emitted from the geo-secondary cache instance. On the geo-primary instance, this metric has no value.
      • The metric is only available in the Premium tier for caches with geo-replication enabled.

    • Geo Replication Healthy

      • Depicts the status of the geo-replication link between caches. There can be two possible states that the replication link can be in:
        • 0 disconnected/unhealthy
        • 1 - healthy
      • The metric is available in the Premium tier caches with geo-replication enabled.
      • In caches on the Premium tier, this metric is only emitted from the geo-secondary cache instance. On the geo-primary instance, this metric has no value.
      • This metric might indicate a disconnected/unhealthy replication status for several reasons, including: monthly patching, host OS updates, network misconfiguration, or failed geo-replication link provisioning.
      • A value of 0 doesn't mean that data on the geo-replica is lost. It just means that the link between geo-primary and geo-secondary is unhealthy.
      • If the geo-replication link is unhealthy for over an hour, file a support request.

  • Gets

    • The number of get operations from the cache during the specified reporting interval. This value is the sum of the following values from the Redis INFO all command: cmdstat_get, cmdstat_hget, cmdstat_hgetall, cmdstat_hmget, cmdstat_mget, cmdstat_getbit, and cmdstat_getrange, and is equivalent to the sum of cache hits and misses during the reporting interval.

  • Operations per Second

    • The total number of commands processed per second by the cache server during the specified reporting interval. This value maps to "instantaneous_ops_per_sec" from the Redis INFO command.

  • Server Load

    • The percentage of CPU cycles in which the Redis server is busy processing and not waiting idle for messages. If this counter reaches 100, the Redis server has hit a performance ceiling, and the CPU can't process work any faster. You can expect a large latency effect. If you're seeing a high Redis Server Load, such as 100, because you're sending many expensive commands to the server, then you might see timeout exceptions in the client. In this case, you should consider scaling up, scaling out to a Premium cluster, or partitioning your data into multiple caches. When Server Load is only moderately high, such as 50 to 80 percent, then average latency usually remains low, and timeout exceptions could have other causes than high server latency.
    • The Server Load metric is sensitive to other processes on the machine using the existing CPU cycles that reduce the Redis server's idle time. For example, on the C1 tier, background tasks such as virus scanning cause Server Load to spike higher for no obvious reason. We recommended that you pay attention to other metrics such as operations, latency, and CPU, in addition to Server Load.

    Caution

    Sometimes Server Load is represented as being over 100. We are investigating this issue. We recommend using the CPU metric instead in the meantime.

  • Sets

    • The number of set operations to the cache during the specified reporting interval. This value is the sum of the following values from the Redis INFO all command: cmdstat_set, cmdstat_hset, cmdstat_hmset, cmdstat_hsetnx, cmdstat_lset, cmdstat_mset, cmdstat_msetnx, cmdstat_setbit, cmdstat_setex, cmdstat_setrange, and cmdstat_setnx.

  • Total Keys

    • The maximum number of keys in the cache during the past reporting time period. This number maps to keyspace from the Redis INFO command. Because of a limitation in the underlying metrics system for caches with clustering enabled, Total Keys return the maximum number of keys of the shard that had the maximum number of keys during the reporting interval.

  • Total Operations

    • The total number of commands processed by the cache server during the specified reporting interval. This value maps to total_commands_processed from the Redis INFO command. When Azure Cache for Redis is used purely for pub/sub, there are no metrics for Cache Hits, Cache Misses, Gets, or Sets, but there are Total Operations metrics that reflect the cache usage for pub/sub operations.

  • Used Memory

    • The amount of cache memory in MB that is used for key/value pairs in the cache during the specified reporting interval. This value maps to used_memory from the Redis INFO command. This value doesn't include metadata or fragmentation.

  • Used Memory Percentage

    • The percent of total memory that is being used during the specified reporting interval. This value references the used_memory value from the Redis INFO command to calculate the percentage. This value doesn't include fragmentation.

  • Used Memory RSS

    • The amount of cache memory used in MB during the specified reporting interval, including fragmentation. This value maps to used_memory_rss from the Redis INFO command.

Resource logs

This section lists the types of resource logs you can collect for this service. The section pulls from the list of all resource logs category types supported in Azure Monitor.

Supported resource logs for Microsoft.Cache/redis

Category Category display name Log table Supports basic log plan Supports ingestion-time transformation Example queries Costs to export
ConnectedClientList Connected client list ACRConnectedClientList

Logs count of Redis clients connected to a cache instance and their IP addresses, logged at a 10-second interval.

 Yes No Queries Yes
MSEntraAuthenticationAuditLog MSEntra authentication audit log No No Yes

Azure Cache for Redis

microsoft.cache/redis

  • ACRConnectedClientList
  • AzureActivity
  • AzureMetrics

Related content