Skip to content

Commit 421607e

Browse files
authored
Merge pull request #122776 from sebsandberg/patch-1
Update monitor-cache-reference.md with caution for total keys
2 parents 5c499bb + de5c564 commit 421607e

File tree

1 file changed

+6
-2
lines changed

1 file changed

+6
-2
lines changed

articles/azure-cache-for-redis/monitor-cache-reference.md

Lines changed: 6 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ description: This article contains important reference material you need when yo
44
ms.date: 05/13/2024
55
ms.custom: horz-monitor
66
ms.topic: reference
7-
author: robb
7+
author: rboucher
88
ms.author: robb
99
ms.service: cache
1010
---
@@ -133,7 +133,11 @@ The following list provides details and more information about the supported Azu
133133
- Sets
134134
- 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`.
135135
- Total Keys
136-
- 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.
136+
- The maximum number of keys in the cache during the past reporting time period. This number maps to `keyspace` from the Redis INFO command.
137+
138+
> [!IMPORTANT]
139+
> 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.
140+
137141
- Total Operations
138142
- 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.
139143
- Used Memory

0 commit comments

Comments
 (0)