Azure Cosmos DB Account (MongoDB) monitoring
- How-to guide
- 5-min read
For information about differences between classic services and other services, see Migrate from Azure classic (formerly "built-in") services to cloud services.
Dynatrace ingests metrics from Azure Metrics API for Azure Cosmos DB Account (MongoDB). You can view metrics for each service instance, split metrics into multiple dimensions, and create custom charts that you can pin to your dashboards.
Prerequisites
- Dynatrace version 1.199+
- Environment ActiveGate version 1.195+
Enable monitoring
To learn how to enable service monitoring, see Enable service monitoring.
View service metrics
You can view the service metrics in your Dynatrace environment either on the custom device overview page or on your Dashboards page.
View metrics on the custom device overview page
To access the custom device overview page
- Go to Technologies & Processes Classic.
- Filter by service name and select the relevant custom device group.
- Once you select the custom device group, you're on the custom device group overview page.
- The custom device group overview page lists all instances (custom devices) belonging to the group. Select an instance to view the custom device overview page.
View metrics on your dashboard
Once you add a service to monitoring, a preset dashboard for the respective service containing all recommended metrics is automatically created on your Dashboards page. You can look for specific dashboards by filtering by Preset and then by Name.
For existing monitored services, you might need to resave your credentials for the preset dashboard to appear on the Dashboards page. To resave your credentials, go to Settings > Cloud and virtualization > Azure, select the desired Azure instance, then select Save.
You can't make changes on a preset dashboard directly, but you can clone and edit it. To clone a dashboard, open the browse menu (…) and select Clone.
To remove a dashboard from the dashboards list, you can hide it. To hide a dashboard, open the browse menu (…) and select Hide.
Hiding a dashboard doesn't affect other users.
Available metrics
This service monitors a part of Azure Cosmos DB Account (Microsoft.DocumentDB/databaseAccounts). While you have this service configured, you can't have Azure Cosmos Database (built-in) service turned on.
| Name | Description | Dimensions | Unit | Recommended |
|---|---|---|---|---|
| Region added | Region Added | Region | Count | |
| Autoscale max throughput | Autoscale Max Throughput | Collection name, Database name | Count |  |
| Account created | Account Created | Count | ||
| Data usage | Total data usage reported at 5 minutes granularity | Collection name, Database name, Region | Byte | |
| Account deleted | Account Deleted | Count | ||
| Document count | Total document count reported at 5 minutes, 1 hour and 1 day granularity | Collection name, Database name, Region | Count | |
| Document quota | Total storage quota reported at 5 minutes granularity | Collection name, Database name, Region | Byte | |
| Index usage | Total index usage reported at 5 minutes granularity | Collection name, Database name, Region | Byte | |
| Metadata requests | Count of metadata requests. Cosmos DB maintains system metadata collection for each account, that allows you to enumerate collections, databases, etc, and their configurations, free of charge. | Collection name, Database name, Region, Status code | Count | |
| Mongo collection created | Mongo Collection Created | Collection name, Database name | Count | |
| Mongo collection deleted | Mongo Collection Deleted | Collection name, Database name | Count | |
| Mongo collection throughput updated | Mongo Collection Throughput Updated | Collection name, Database name | Count | |
| Mongo collection updated | Mongo Collection Updated | Collection name, Database name | Count | |
| Mongo database deleted | Mongo Database Deleted | Database name | Count | |
| Mongo database throughput updated | Mongo Database Throughput Updated | Database name | Count | |
| Mongo database created | Mongo Database Created | Database name | Count | |
| Mongo database updated | Mongo Database Updated | Database name | Count | |
| Mongo request charge | Mongo Request Units Consumed | Collection name, Command name, Database name, Error code, Region, Status | Count | |
| Mongo requests | Number of Mongo Requests Made | Collection name, Command name, Database name, Error code, Region, Status | Count | |
| Normalized ru consumption | Max RU consumption percentage per minute | Collection name, Collection rid, Database name, Partition key range ID, Physical partition ID, Region | Percent | |
| Region offlined | Region Offlined | Region, Status code | Count | |
| Region onlined | Region Onlined | Region, Status code | Count | |
| Physical partition size | Physical Partition Size in bytes | Collection name, Database name, Resource ID, Physical partition ID, Region | Byte | |
| Physical partition throughput | Physical Partition Throughput | Collection name, Database name, Resource ID, Physical partition ID, Region | Count | |
| Provisioned throughput | Provisioned Throughput | Collection name, Database name | Count | |
| Region failed over | Region Failed Over | Count | ||
| Region removed | Region Removed | Region | Count | |
| P99 replication latency | P99 Replication Latency across source and target regions for geo-enabled account | Source region, Target region | MilliSecond | |
| Server side latency | Server Side Latency | Collection name, Connection mode, Database name, Operation type, Publicapi type, Region | MilliSecond | |
| Server side latency direct | Server Side Latency in Direct Connection Mode | Collection name, Database name, Operation type, Publicapi type, Region | MilliSecond | |
| Server side latency gateway | Server Side Latency in Gateway Connection Mode | Collection name, Database name, Operation type, Publicapi type, Region | MilliSecond | |
| Service availability | Account requests availability at one hour, day or month granularity | Percent | | |
| Total requests | Number of requests made | Capacity type, Collection name, Database name, Operation type, Region, Status, Status code | Count | |
| Total request units | SQL Request Units consumed | Capacity type, Collection name, Database name, Operation type, Region, Status, Status code | Count | |
| Account keys updated | Account Keys Updated | Key type | Count | |
| Account network settings updated | Account Network Settings Updated | Count | ||
| Account replication settings updated | Account Replication Settings Updated | Count | ||
| Account diagnostic settings updated | Account Diagnostic Settings Updated | Diagnostic settings name, Resource group name | Count |