Redis cache with no clients and no lookups
An Azure Cache for Redis instance that nothing has connected to or read from.
Why it happens
A Redis cache bills a fixed hourly rate for as long as it exists, independently of traffic: a Premium P1 is about $405 a month and a Standard C1 about $101. Sustained zero on both connected clients and key lookups means the cache is serving nobody while charging in full. Both signals are required because either alone can be innocent, since an idle connection pool holds clients against a cache nothing reads and a health probe can produce lookups without a lasting connection.
What the agent does about it
An Azure Cache for Redis instance that nothing has connected to or read from.
It will not fix this one
It reports this and takes no action. A check only earns the right to change something once the action behind it can re-read live state before it fires and knows the way back.
Related checks
Idle virtual machine
A running VM whose CPU and network have been near zero for the whole window.
Oversized virtual machine
A running VM whose sustained peak fits comfortably inside the next size down.
Unattached managed disk
A managed disk attached to nothing, billing its full provisioned size every month.