Systems Management Associates

Hotrod

Foglight for Azure Cosmos DB

Request units, latency, and availability in one account view

Topology
Account-keyed (CosmosAccount)
Data source
FglAM agent using OAuth2 client credentials against Azure AD, then Azure Monitor metrics plus the DocumentDB ARM resource provider.
Dashboards
12 purpose-built views

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

The cartridge is account-keyed: the CosmosAccount is the DomainRoot topology object, with databases, containers, and regions rolling up beneath it. Service-principal tenant, client ID, secret, subscription, resource group, and account name are agent properties - no software runs inside the Azure account beyond the credentials the agent uses.

Twelve purpose-built dashboards span Overview, Throughput, Requests & Latency, Storage, Databases, Containers, Regions, Workload, Resource, I/O, Performance, and Contention. A comprehensive ruleset covers availability, RU saturation, throttling, latency, storage, gateway CPU, cache hit rate, and server errors.

Dashboards

OverviewThroughputRequests & LatencyStorageDatabasesContainersRegionsWorkloadResourceI/OPerformanceContention

Ready to see Azure Cosmos DB in action?

Request a free trial or talk to our engineers about your environment.