You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/cosmos-db/monitor.md
+13-14Lines changed: 13 additions & 14 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -44,7 +44,7 @@ At a minimum your service should have the following two articles:
44
44
45
45
Azure Cosmos DB insights is a feature based on the [workbooks feature of Azure Monitor](/azure/azure-monitor/visualize/workbooks-overview). Use Azure Cosmos DB insights for a view of the overall performance, failures, capacity, and operational health of all your Azure Cosmos DB resources in a unified interactive experience.
46
46
47
-
For more information about Azure Cosmos DB insights, see [Azure Cosmos DB insights](insights-overview.md) and [Scenarios to monitor](../use-metrics.md).
47
+
For more information about Azure Cosmos DB insights, see [Azure Cosmos DB insights](insights-overview.md) and [Scenarios to monitor](use-metrics.md).
For information about partner solutions and tools that can help monitor Azure Cosmos DB, see [Monitor Azure Cosmos DB using third-party solutions](../monitoring-solutions.md).
81
+
For information about partner solutions and tools that can help monitor Azure Cosmos DB, see [Monitor Azure Cosmos DB using third-party solutions](monitoring-solutions.md).
82
+
83
+
To implement Micrometer metrics in the Java SDK for Azure Cosmos DB by consuming Prometheus metrics, see [Use Micrometer client metrics for Java](nosql/client-metrics-java.md).
84
84
85
85
<!-- METRICS SECTION END ------------------------------------->
86
86
@@ -115,6 +115,8 @@ If your service has other logs that aren't resource logs or in the activity log,
You can use Azure Monitor Metrics Explorer to analyze metrics for Azure Cosmos DB with metrics from other Azure services by opening **Metrics** from the **Azure Monitor** menu. For more information about how to use metrics explorer, see [Analyze metrics with Azure Monitor metrics explorer](/azure/azure-monitor/essentials/analyze-metrics).
@@ -132,8 +134,6 @@ For more information and detailed instructions, see the following articles:
132
134
133
135
For a list of all resource metrics supported in Azure Monitor, see [Supported Azure Monitor metrics](/azure/azure-monitor/essentials/metrics-supported). For a list of the platform metrics collected for Azure Cosmos DB, see [Monitoring Azure Cosmos DB data reference metrics](monitor-reference.md#metrics).
134
136
135
-
To implement Micrometer metrics in the Java SDK for Azure Cosmos DB by consuming Prometheus metrics, see [Use Micrometer client metrics for Java](nosql/client-metrics-java.md)
136
-
137
137
### Monitor Azure Cosmos DB programmatically
138
138
139
139
The account level metrics available in the portal, such as account storage usage and total requests, aren't available by using the API for NoSQL. However, you can retrieve usage data at the collection level by using the API for NoSQL. To retrieve collection level data, use one of the following approaches:
@@ -154,7 +154,7 @@ To retrieve individual metrics, use the following format:
To learn more, see [Azure monitoring REST API](../azure-monitor/essentials/rest-api-walkthrough.md).
157
+
To learn more, see [Azure monitoring REST API](/azure/azure-monitor/essentials/rest-api-walkthrough).
158
158
159
159
### Analyze Azure Cosmos DB logs
160
160
@@ -164,11 +164,10 @@ For the types of resource logs collected for Azure Cosmos DB, see [Azure Cosmos
164
164
165
165
See the following articles for more information about working with Azure Monitor Logs for Azure Cosmos DB:
166
166
167
-
-[Monitor data by using Azure Diagnostic settings](../monitor-resource-logs.md)
168
-
[Audit control plane logs](../audit-control-plane-logs.md) Use diagnostic logs to audit control plane operations in Azure Cosmos DB accounts or containers.
169
-
[Add a transformation for workspace data](../tutorial-log-transformation.md) Use a workspace data collection rule (DCR) to apply transformations to log data flowing into Azure Cosmos DB.
170
-
[Use Micrometer client metrics for Java](client-metrics-java.md) Implement Micrometer metrics in the Java SDK for Azure Cosmos DB by consuming Prometheus metrics.
171
-
167
+
-[Monitor data by using Azure Diagnostic settings](monitor-resource-logs.md)
168
+
[Audit control plane logs](audit-control-plane-logs.md)
169
+
[Add a transformation for workspace data](tutorial-log-transformation.md)
170
+
[Use Micrometer client metrics for Java](client-metrics-java.md)
172
171
173
172
<!-- ### Sample Kusto queries. Required section. If you have sample Kusto queries for your service, add them after the include. -->
For Kusto queries you can use to troubleshoot issues with Azure Cosmos DB, see the following articles:
268
267
269
-
-[Troubleshoot issues by using basic queries](../monitor-logs-basic-queries.md)
268
+
-[Troubleshoot issues by using basic queries](monitor-logs-basic-queries.md)
270
269
-[Troubleshoot issues by using advanced diagnostics queries](diagnostic-queries.md)
271
270
272
271
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).
@@ -298,7 +297,7 @@ The following table lists some common and recommended alert rules for Azure Cosm
298
297
|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. |
299
298
|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. |
300
299
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).
300
+
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).
0 commit comments