Hi Sujina S J •,,
Thanks for your patience.
I have got the below reply from the internal team that it is a normal behavior and expected:
`Azure Cache for redis does have internal monitoring processes which connect to and send a small number of commands to the customer’s redis cache, in order to measure and ensure its availability.
Used memory also includes some basic ‘overhead’ of the redis processes, plus resource usage for client connections, network buffering, and so on; not just the memory used by customer keys.
We could investigate resource usage in a little more detail if they come with the name of the cache, or at least have more clarify on what SKU the question is about, but what they describe sounds like normal behavior.`
For above mentioned investigation, I would recommend you to raise support case so that it could be deeply investigated for your Redis Cache.
Adding to above, the “Cache Read” and “Cache Write” metrics are measured at the network level. So, activity here doesn’t necessarily correlate 1:1 with actual GET/SET commands in Redis, but instead may be due to internal processes pinging each Redis node.
Hope this helps. If this answers your query, do click Accept Answer
and Mark Helpful
for the same. And, if you have any further query do let us know.
Thank you.