#Active events cosmo run full

The following sections build on this article by describing the specific data gathered from Azure Cosmos DB and providing examples for configuring data collection and analyzing this data with Azure tools. Standard tools in Azure for analyzing and alerting on monitoring data.If you're not already familiar with monitoring Azure services, start with the article Monitoring Azure resources with Azure Monitor, which describes the following concepts:

#Active events cosmo run full

What is Azure Monitor?Īzure Cosmos DB creates monitoring data using Azure Monitor, which is a full stack monitoring service in Azure that provides a complete set of features to monitor your Azure resources in addition to resources in other clouds and on-premises. You can enable other types of data collection with some configuration. Some of this data is collected automatically and is available for analysis as soon as you create the resource. This information is helpful, however only a small amount of the monitoring data is available from this pane. The Overview page in the Azure portal for each Azure Cosmos DB account includes a brief view of the resource usage, such as total requests, requests that resulted in a specific HTTP status code, and hourly billing. This information is also required if you need to reach out to the Azure Cosmos DB support team. When using Azure Cosmos DB, at the client-side you can collect the details for request charge, activity ID, exception/stack trace information, HTTP status/sub-status code, diagnostic string to debug any issue that might occur. The following image shows different options available to monitor Azure Cosmos DB account through Azure portal: To learn more, see the Monitoring Azure Cosmos DB programmatically section of this article. NET, Java, Python, Node.js SDKs, and the headers in REST API. Monitor programmatically with SDKs: You can monitor your Azure Cosmos account programmatically by using the. To learn more, see the Analyze log data section of this article. You can analyze these logs by running queries on the gathered data. For example, if the throughput of a container is changes, the properties of a Cosmos account are changed these events are captures within the logs. Data such as events and traces that occur at a second granularity are stored as logs.

Monitor with diagnostic logs in Azure Monitor: You can monitor the logs of your Azure Cosmos account and create dashboards from the Azure Monitor. To learn more, see the Analyze metric data section of this article. So you need to use case-insensitive comparison when doing string comparisons on these dimension values. The dimension values for the metrics such as container name are case-insensitive. Most of the metrics that are available from the previous options are also available in these metrics. By default, these metrics have a retention period of 30 days. These metrics are collected with one-minute granularity, the granularity may vary based on the metric you choose. Azure Monitor collects the Azure Cosmos DB metrics by default, you will not need to explicitly configure anything. Monitor with metrics in Azure monitor: You can monitor the metrics of your Azure Cosmos account and create dashboards from the Azure Monitor. To learn more, see the Monitoring data collected from Azure Cosmos DB section of this article. By default, these metrics have a retention period of seven days. The metrics on this tab include throughput, storage, availability, latency, consistency, and system level metrics. Monitor from Azure Cosmos DB portal: You can monitor with the metrics available within the Metrics tab of the Azure Cosmos account. When using server-side metrics, you can monitor the data stored in Azure Cosmos DB with the following options: You can monitor your data with client-side and server-side metrics.

This article describes the monitoring data generated by Azure Cosmos databases and how you can use the features of Azure Monitor to analyze and alert on this data. When you have critical applications and business processes relying on Azure resources, you want to monitor those resources for their availability, performance, and operation.