Skip to content

Commit d8ff3a4

Browse files
Merge pull request #219179 from flang-msft/fxl---Provide-recommendations-for-which-metrics-to-use-for-clustered-caches-14977378
fxl---added text from work item 14977378
2 parents 3f58aa9 + 6d74522 commit d8ff3a4

File tree

1 file changed

+4
-0
lines changed

1 file changed

+4
-0
lines changed

articles/azure-cache-for-redis/cache-how-to-monitor.md

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -125,6 +125,10 @@ The types **Count** and **“Sum** can be misleading for certain metrics (connec
125125
> Even when the cache is idle with no connected active client applications, you might see some cache activity, such as connected clients, memory usage, and operations being performed. The activity is normal in the operation of cache.
126126
>
127127
128+
For non-clustered caches, we recommend using the metrics without the suffix `Instance Based`. For example, to check server load for your cache instance, use the metric `Server Load`.
129+
130+
In contrast, for clustered caches, we recommend using 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`.
131+
128132
## List of metrics
129133

130134
- Cache Latency (preview)

0 commit comments

Comments
 (0)