Hotrod
Foglight for Azure Cosmos DB
Request units, latency, and availability in one account view
Description
Azure Cosmos DB is Microsoft's globally distributed, multi-model NoSQL database service. Teams choose it for elastic throughput measured in request units (RUs), single-digit millisecond reads and writes at any scale, and turnkey multi-region replication for mission-critical applications.
Foglight for Azure Cosmos DB is an SMA cloud-API cartridge. Its FglAM agent authenticates with an Azure AD service principal and collects Azure Monitor metrics together with control-plane inventory from the Cosmos DB resource provider - databases, containers, regions, and provisioned throughput - without Cosmos account keys or JDBC.
Business Challenge
Cosmos DB exposes rich metrics in Azure Monitor, but throttling (HTTP 429), RU saturation, rising server-side latency, and storage growth are easy to miss when each signal lives in a separate portal blade. Platform teams need history, roll-up health, and alerting tuned to how Cosmos actually behaves under load.
Foglight for Azure Cosmos DB treats the database account as the top-level monitored object, correlating requests, RUs, availability, latency, storage, and contention in one console with the Foglight Rules Engine watching the conditions that precede an outage.
Key Features
Treat the Cosmos account as one health surface. Databases, containers, and regions roll up so throttling, RU saturation, and latency are not buried in separate portal blades.
Twelve dashboards cover throughput, requests, storage, regions, and contention, with alerting on the conditions that typically precede an outage — without Cosmos account keys or anything running inside Azure.
Dashboards
Screenshots
Ready to see Foglight for Azure Cosmos DB in action?
Request a free trial or talk to our engineers about your environment.