Question

Your team runs a production Azure Cosmos DB for NoSQL container provisioned with autoscale at a maximum of 10,000 RU/s. Users report intermittent HTTP 429 responses during peak hours, yet the total RU/s consumed across the account stays well below the 10,000 RU/s ceiling in Azure Monitor. Which metric should you examine first to confirm the most likely root cause of the throttling?

Accepted Answer

Normalized RU Consumption, to detect whether a single physical partition is hitting its per-partition throughput limit

Answer

Server-Side Latency, to determine whether slow query execution is causing the 429 responses

Answer

Data Usage, to confirm whether the container has exceeded its storage quota

Answer

Total Request Units, averaged over the full account, to verify overall provisioning is adequate