Skip to content

Commit 7107c21

Browse files
v-thepetv-thepet
committed
fixes
1 parent 528946c commit 7107c21

File tree

2 files changed

+58
-11
lines changed

2 files changed

+58
-11
lines changed

‎articles/cosmos-db/monitor-reference.md

Lines changed: 55 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -60,6 +60,8 @@ The following table lists the metrics available for the Microsoft.DocumentDB/mon
6060

6161
### Metrics by category
6262

63+
The following tables list Azure Cosmos DB metrics categorized by metric type.
64+
6365
#### Request metrics
6466

6567
|Metric (Metric Display Name)|Unit (Aggregation Type) |Description|Dimensions| Time granularities| Legacy metric mapping | Usage |
@@ -115,11 +117,47 @@ The following table lists the metrics available for the Microsoft.DocumentDB/mon
115117
<!-- Use one of the following includes, depending on whether you have metrics with dimensions.
116118
- If you have metrics with dimensions, use the following include and list the metrics with dimensions after the include. For an example, see https://learn.microsoft.com/azure/storage/common/monitor-storage-reference#metrics-dimensions. Questions: email [email protected]. -->
117119
[!INCLUDE [horz-monitor-ref-metrics-dimensions](~/articles/reusable-content/ce-skilling/azure/includes/azure-monitor/horizontals/horz-monitor-ref-metrics-dimensions.md)]
118-
**Microsoft.DocumentDB/DatabaseAccounts:** CollectionName, DatabaseName, OperationType, Region, Status, StatusCode, ApiKind, ApiKindResourceType, APIType, ApplicationType, BuildType, CacheEntryType, CacheExercised, CacheHit, CapacityType, ChildResourceName, ClosureReason, CommandName, ConnectionMode, DiagnosticSettingsName, Error, ErrorCode, IsExternal, IsSharedThroughputOffer, IsThroughputRequest, KeyType, MetricType, NotStarted, OfferOwnerRid, PartitionKeyRangeId, PhysicalPartitionId, PriorityLevel, PublicAPIType, ReplicationInProgress, ResourceGroupName, ResourceName, Role, SourceRegion, TargetContainerName, TargetRegion
119-
120-
**Microsoft.DocumentDB/cassandraClusters:** cassandra_datacenter, cassandra_node, cache_name
121-
122-
**Microsoft.DocumentDB/mongoClusters:** ServerName
120+
|Namespace|Dimension|
121+
|---------|---------|
122+
|Microsoft.DocumentDB/DatabaseAccounts|ApiKind|
123+
|Microsoft.DocumentDB/DatabaseAccounts|ApiKindResourceType|
124+
|Microsoft.DocumentDB/DatabaseAccounts|APIType|
125+
|Microsoft.DocumentDB/DatabaseAccounts|ApplicationType|
126+
|Microsoft.DocumentDB/DatabaseAccounts|BuildType|
127+
|Microsoft.DocumentDB/DatabaseAccounts|CacheEntryType|
128+
|Microsoft.DocumentDB/DatabaseAccounts|CacheExercised|
129+
|Microsoft.DocumentDB/DatabaseAccounts|CacheHit|
130+
|Microsoft.DocumentDB/DatabaseAccounts|CapacityType|
131+
|Microsoft.DocumentDB/DatabaseAccounts|ChildResourceName|
132+
|Microsoft.DocumentDB/DatabaseAccounts|ClosureReason|
133+
|Microsoft.DocumentDB/DatabaseAccounts|CommandName|
134+
|Microsoft.DocumentDB/DatabaseAccounts|ConnectionMode|
135+
|Microsoft.DocumentDB/DatabaseAccounts|DiagnosticSettingsName|
136+
|Microsoft.DocumentDB/DatabaseAccounts|Error|
137+
|Microsoft.DocumentDB/DatabaseAccounts|ErrorCode|
138+
|Microsoft.DocumentDB/DatabaseAccounts|IsExternal|
139+
|Microsoft.DocumentDB/DatabaseAccounts|IsSharedThroughputOffer|
140+
|Microsoft.DocumentDB/DatabaseAccounts|IsThroughputRequest|
141+
|Microsoft.DocumentDB/DatabaseAccounts|KeyType|
142+
|Microsoft.DocumentDB/DatabaseAccounts|MetricType|
143+
|Microsoft.DocumentDB/DatabaseAccounts|NotStarted|
144+
|Microsoft.DocumentDB/DatabaseAccounts|OfferOwnerRid|
145+
|Microsoft.DocumentDB/DatabaseAccounts|PartitionKeyRangeId|
146+
|Microsoft.DocumentDB/DatabaseAccounts|PhysicalPartitionId|
147+
|Microsoft.DocumentDB/DatabaseAccounts|PhysicalPartitionId|
148+
|Microsoft.DocumentDB/DatabaseAccounts|PriorityLevel|
149+
|Microsoft.DocumentDB/DatabaseAccounts|PublicAPIType|
150+
|Microsoft.DocumentDB/DatabaseAccounts|ReplicationInProgress|
151+
|Microsoft.DocumentDB/DatabaseAccounts|ResourceGroupName|
152+
|Microsoft.DocumentDB/DatabaseAccounts|ResourceName|
153+
|Microsoft.DocumentDB/DatabaseAccounts|Role|
154+
|Microsoft.DocumentDB/DatabaseAccounts|SourceRegion|
155+
|Microsoft.DocumentDB/DatabaseAccounts|TargetContainerName|
156+
|Microsoft.DocumentDB/DatabaseAccounts|TargetRegion|
157+
|Microsoft.DocumentDB/cassandraClusters|cassandra_datacenter|
158+
|Microsoft.DocumentDB/cassandraClusters|cassandra_node|
159+
|Microsoft.DocumentDB/cassandraClusters|cache_name|
160+
|Microsoft.DocumentDB/mongoClusters|ServerName|
123161

124162
<!-- ## Resource logs. Required section. -->
125163
[!INCLUDE [horz-monitor-ref-resource-logs](~/articles/reusable-content/ce-skilling/azure/includes/azure-monitor/horizontals/horz-monitor-ref-resource-logs.md)]
@@ -150,9 +188,19 @@ Microsoft.DocumentDb/databaseAccounts
150188
- [CDBGremlinRequests](/azure/azure-monitor/reference/tables/CDBGremlinRequests#columns)
151189
- [CDBControlPlaneRequests](/azure/azure-monitor/reference/tables/CDBControlPlaneRequests#columns)
152190
- [AzureMetrics](/azure/azure-monitor/reference/tables/AzureMetrics#columns)
153-
- [AzureDiagnostics](/azure/azure-monitor/reference/tables/AzureDiagnostics#columns)
191+
- [AzureDiagnostics](/azure/azure-monitor/reference/tables/AzureDiagnostics#columns). Logs are collected in the **AzureDiagnostics** table under the resource provider name of `MICROSOFT.DOCUMENTDB`.
192+
193+
### Azure Managed Instance for Apache Cassandra
194+
Microsoft.DocumentDB/cassandraClusters
195+
196+
- [AzureActivity](/azure/azure-monitor/reference/tables/AzureActivity#columns)
197+
- [CassandraAudit](/azure/azure-monitor/reference/tables/CassandraAudit#columns)
198+
- [CassandraLogs](/azure/azure-monitor/reference/tables/CassandraLogs#columns)
199+
200+
### Azure Cosmos DB for MongoDB (vCore)
201+
Microsoft.DocumentDB/mongoClusters
154202

155-
Logs are collected in the **AzureDiagnostics** table under the resource provider name of `MICROSOFT.DOCUMENTDB`.
203+
- [VCoreMongoRequests](/azure/azure-monitor/reference/tables/VCoreMongoRequests#columns)
156204

157205
### Azure CosmosDB resource logs properties
158206

‎articles/cosmos-db/monitor.md

Lines changed: 3 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -125,7 +125,7 @@ You can use Azure Monitor Metrics Explorer to analyze metrics for Azure Cosmos D
125125

126126
You can monitor server-side latency, request unit usage, and normalized request unit usage for your Azure Cosmos DB resources. You can select metrics specific to request units, storage, latency, availability, Cassandra, and others.
127127

128-
On the client side, you can collect the details for request charge, activity ID, exception and stack trace information, HTTP status and substatus code, and diagnostic string to debug issues that might occur.
128+
On the client side, you can debug issues by collecting metrics for request charge, activity ID, exception and stack trace information, HTTP status and substatus code, and diagnostic string.
129129

130130
For more information and detailed instructions, see the following articles:
131131

@@ -267,7 +267,7 @@ AzureDiagnostics
267267
For Kusto queries you can use to troubleshoot issues with Azure Cosmos DB, see the following articles:
268268

269269
- [Troubleshoot issues by using basic queries](monitor-logs-basic-queries.md)
270-
- [Troubleshoot issues by using advanced diagnostics queries](diagnostic-queries.md)
270+
- [Troubleshoot issues by using advanced diagnostic queries](nosql/diagnostic-queries.md)
271271

272272
These examples are just a small sampling of the rich queries you can run in Azure Monitor by using the Kusto Query Language (KQL). For more examples, see [samples for Kusto queries](/azure/data-explorer/kusto/query/samples?pivots=azuremonitor).
273273

@@ -298,8 +298,7 @@ The following table lists some common and recommended alert rules for Azure Cosm
298298
|Region failed over |Operator: *Greater than*, Aggregation type: *Count*, Threshold value: 1 | When a single region is failed over. This alert is helpful if you didn't enable service-managed failover. |
299299
|Rotate keys (activity log alert)| Event level: *Informational*, *Status*: started| Alerts when the account keys are rotated. You can update your application with the new keys. |
300300

301-
- For more information and instructions on creating alerts for Azure Cosmos DB, see [Create alert on metrics](create-alerts.md).
302-
- To create an alert to monitor if storage for a logical partition key is approaching 20 GB, see [Create alert on logical partition key size](how-to-alert-on-logical-partition-key-storage-size.md).
301+
For more information and instructions on creating alerts for Azure Cosmos DB, see [Create alert on metrics](create-alerts.md). To create an alert to monitor if storage for a logical partition key is approaching 20 GB, see [Create alert on logical partition key size](how-to-alert-on-logical-partition-key-storage-size.md).
303302

304303
<!-- ### Advisor recommendations. Required section. -->
305304
[!INCLUDE [horz-monitor-advisor-recommendations](~/articles/reusable-content/ce-skilling/azure/includes/azure-monitor/horizontals/horz-monitor-advisor-recommendations.md)]

0 commit comments

Comments
 (0)