Skip to content

Commit 9ac56d7

Browse files
committed
changes
1 parent 5eb999c commit 9ac56d7

File tree

1 file changed

+13
-14
lines changed

1 file changed

+13
-14
lines changed

articles/cosmos-db/monitor.md

Lines changed: 13 additions & 14 deletions
Original file line numberDiff line numberDiff line change
@@ -44,7 +44,7 @@ At a minimum your service should have the following two articles:
4444

4545
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.
4646

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).
4848

4949
<!-- ## Resource types. Required section. -->
5050
[!INCLUDE [horz-monitor-resource-types](~/articles/reusable-content/ce-skilling/azure/includes/azure-monitor/horizontals/horz-monitor-resource-types.md)]
@@ -62,8 +62,6 @@ For more information about the resource types for Azure Cosmos DB, see [Azure Co
6262
[!INCLUDE [horz-monitor-platform-metrics](~/articles/reusable-content/ce-skilling/azure/includes/azure-monitor/horizontals/horz-monitor-platform-metrics.md)]
6363
For a list of available metrics for Azure Cosmos DB, see [Azure Cosmos DB monitoring data reference](monitor-reference.md#metrics).
6464

65-
66-
6765
<!-- Platform metrics service-specific information. Add service-specific information about your platform metrics here.-->
6866

6967
<!-- ## Prometheus/container metrics. Optional. If your service uses containers/Prometheus metrics, add the following include and information.
@@ -80,7 +78,9 @@ Custom imported service-specific information. Add service-specific information a
8078

8179
<!-- ## Non-Azure Monitor metrics. Optional. If your service uses any non-Azure Monitor based metrics, add the following include and information.-->
8280
[!INCLUDE [horz-monitor-custom-metrics](~/articles/reusable-content/ce-skilling/azure/includes/azure-monitor/horizontals/horz-monitor-non-monitor-metrics.md)]
83-
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).
8484

8585
<!-- METRICS SECTION END ------------------------------------->
8686

@@ -115,6 +115,8 @@ If your service has other logs that aren't resource logs or in the activity log,
115115
<!-- ### External tools. Required section. -->
116116
[!INCLUDE [horz-monitor-external-tools](~/articles/reusable-content/ce-skilling/azure/includes/azure-monitor/horizontals/horz-monitor-external-tools.md)]
117117

118+
<a name="analyzing-metrics"></a>
119+
<a name="view-operation-level-metrics-for-azure-cosmos-db"></a>
118120
### Analyze Azure Cosmos DB metrics
119121

120122
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:
132134

133135
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).
134136

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-
137137
### Monitor Azure Cosmos DB programmatically
138138

139139
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:
154154
https://management.azure.com/subscriptions/{SubscriptionId}/resourceGroups/{ResourceGroup}/providers/Microsoft.DocumentDb/databaseAccounts/{DocumentDBAccountName}/providers/microsoft.insights/metrics?timespan={StartTime}/{EndTime}&interval={AggregationInterval}&metricnames={MetricName}&aggregation={AggregationType}&`$filter={Filter}&api-version=2018-01-01
155155
```
156156

157-
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).
158158

159159
### Analyze Azure Cosmos DB logs
160160

@@ -164,11 +164,10 @@ For the types of resource logs collected for Azure Cosmos DB, see [Azure Cosmos
164164

165165
See the following articles for more information about working with Azure Monitor Logs for Azure Cosmos DB:
166166

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)
172171

173172
<!-- ### Sample Kusto queries. Required section. If you have sample Kusto queries for your service, add them after the include. -->
174173
[!INCLUDE [horz-monitor-kusto-queries](~/articles/reusable-content/ce-skilling/azure/includes/azure-monitor/horizontals/horz-monitor-kusto-queries.md)]
@@ -266,7 +265,7 @@ AzureDiagnostics
266265

267266
For Kusto queries you can use to troubleshoot issues with Azure Cosmos DB, see the following articles:
268267

269-
- [Troubleshoot issues by using basic queries](../monitor-logs-basic-queries.md)
268+
- [Troubleshoot issues by using basic queries](monitor-logs-basic-queries.md)
270269
- [Troubleshoot issues by using advanced diagnostics queries](diagnostic-queries.md)
271270

272271
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
298297
|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. |
299298
|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. |
300299

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).
302301

303302
<!-- ### Advisor recommendations. Required section. -->
304303
[!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)