You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For more details and information about the supported metrics for Microsoft.Cache/redis and Microsoft.Cache/redisEnterprise, see [List of metrics](monitor-cache-reference.md#azure-cache-for-redis-metrics).
21
21
22
22
### Supported metrics for Microsoft.Cache/redis
23
23
The following table lists the metrics available for the Microsoft.Cache/redis resource type.
@@ -142,15 +142,15 @@ The following list provides details and more information about the supported Azu
142
142
- Used Memory RSS
143
143
- 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. This metric isn't available in Enterprise or Enterprise Flash tier caches.
Insights for Azure Cache for Redis deliver the following experience:
19
19
@@ -25,18 +25,18 @@ Insights for Azure Cache for Redis don't require you to enable or configure anyt
25
25
26
26
To learn how to view, configure, and customize insights for Azure Cache for Redis, see [Azure Monitor insights for Azure Cache for Redis](cache-insights-overview.md).
For more information about the resource types for Azure Cache for Redis, see [Azure Cache for Redis monitoring data reference](monitor-cache-reference.md).
For the available resource log categories, their associated Log Analytics tables, and the logs schemas for Azure Cache for Redis, see [Azure Cache for Redis monitoring data reference](monitor-cache-reference.md#resource-logs).
42
42
## Azure Cache for Redis resource logs
@@ -56,11 +56,11 @@ Azure Cache for Redis uses Azure diagnostic settings to log information on clien
56
56
57
57
The connection logs have slightly different implementations, contents, and setup procedures for the different Azure Cache for Redis tiers. For details, see [Azure Monitor diagnostic settings](cache-monitor-diagnostic-settings.md).
@@ -87,11 +87,11 @@ For nonclustered caches, it's best to use the metrics without the suffix `Instan
87
87
88
88
In contrast, for clustered caches, use the metrics with the suffix `Instance Based`. Then, add a split or filter on `ShardId`. For example, to check the server load of shard 1, use the metric **Server Load (Instance Based)**, then apply filter **ShardId = 1**.
For sample Kusto queries for Azure Cache for Redis connection logs, see [Connection log queries](cache-monitor-diagnostic-settings.md#log-analytics-queries).
@@ -103,7 +103,7 @@ The following table lists common and recommended alert rules for Azure Cache for
103
103
|Metric |High `Server Load` usage or spikes |High server load means the Redis server is unable to keep up with requests, leading to timeouts or slow responses. Create alerts on metrics on server load metrics to be notified early about potential impacts.|
104
104
|Metric |High network bandwidth usage |If the server exceeds the available bandwidth, then data isn't sent to the client as quickly. Client requests could time out because the server can't push data to the client fast enough. Set up alerts for server-side network bandwidth limits by using the `Cache Read` and `Cache Write` counters. |
0 commit comments