🛡️ Azure Redis Cache has no cache lookups for 30 days🟢

• Contextual name: 🛡️ Redis Cache has no cache lookups for 30 days🟢
• ID: /ce/ca/azure/redis-cache/no-cache-lookups-in-30-days
• Tags:
  • 🟢 Policy with categories
  • 🟢 Policy with type
  • 🟢 Production policy
• Policy Type: BEST_PRACTICE
• Policy Categories: COST

Stats

not available

Logic

• 🧠 prod.logic.yaml🟢
  • 📗 Azure Redis Cache
  • 🔌 Azure Redis Cache - object.extracts.yaml
  • 🧪 test-data.json

Description

Open File

Description

This review-only policy identifies successfully provisioned Azure Cache for Redis instances that have recorded zero cache hits and zero cache misses over 30 days.

Rationale

A cache with no lookup activity may be idle while continuing to incur cost. The metrics are not conclusive usage evidence because Redis can also support pub/sub, locks, queues, sessions, and other patterns that do not produce cache hits or misses.

Impact

Removing or resizing a cache without checking those other patterns can interrupt applications. Treat every result as an investigation, not as an automatic deletion recommendation.

Audit

This policy evaluates an Azure Cache for Redis instance based on its 30-day cache lookup metrics.

The Azure Cache for Redis instance is marked as INCOMPLIANT if:

• Monitor: Cache Hits, 30-Day = 0.
• Monitor: Cache Misses, 30-Day = 0.

The instance is marked as INAPPLICABLE if its Provisioning State is not Succeeded.

The instance is marked as UNDETERMINED if its provisioning state or either

... see more

Remediation

Open File

Remediation

Zero cache hits and misses do not prove that the instance is unused. Redis can support workloads that do not perform cache lookups, so do not delete or resize the instance based on this finding alone.

Validate the Finding

1. Identify the instance owner and the applications that connect to it.
2. In Azure Monitor, select a representative period of at least 30 days and review Cache Hits, Cache Misses, Total Commands Processed, Connected Clients, Cache Read, and Cache Write.
3. Check application configuration and operational records for pub/sub, streams, distributed locks, queues, sessions, scheduled workloads, and other Redis uses that may not produce cache hits or misses.
4. Confirm whether the observed period includes normal business cycles and any expected seasonal or batch activity.

Remediate

• If the instance supports a required non-cache workload, retain it and document its owner and purpose.
• If the instance is required but oversized, evaluate a smaller supported tier or capacity. Test workload limits, availability, performance, and rollback before

... see more

policy.yaml

Open File

Linked Framework Sections

Section	Sub Sections	Internal Rules	Policies	Flags	Compliance
💼 Cloudaware Framework → 💼 Waste Reduction			30		no data