Do we have cost visibility around this
Are queries consuming high RUs due to poor filters or cross-partition scans?
Review oversized Redis/AMR instances.
Review Mongo vCore cluster sizing and usage patterns to ensure compute, storage, backup, and environment configuration are aligned with actual workload needs.
Do we have idle or rarely used clusters?
Is storage growing due to unused or test data?
Are diagnostic settings consistent across products?
Review diagnostic logging, metrics, and retention configuration to avoid unnecessary monitoring cost .
uncontrolled logging becomes expensive.
Do any Emerging DB non-prod resources support scheduled scale-down or reduced capacity during non-business hours?”
Objective: Review whether Cosmos containers are indexing all fields unnecessarily.
Why it matters: excessive indexing can increase RU consumption during writes.
“Can we review if Cosmos indexing policies are optimized, especially for containers with heavy write activity?”
Can we review memory utilization versus allocated SKU for Redis/AMR and identify right-sizing opportunities?”
Policy expiration review
Where we allow high SKU, HA, autoscale, persistence, or geo-replication by exception, can we add review/expiry so exceptions don’t stay forever?
Can we define standard lower-environment templates for Cosmos, vCore, and AMR so teams don’t accidentally provision production-like configurations?
0 comments:
Post a Comment