Skip to content

Commit 788994f

Browse files
committed
added system and db metrics
1 parent f36d858 commit 788994f

File tree

4 files changed

+18
-8
lines changed

4 files changed

+18
-8
lines changed

articles/cosmos-db/mongodb/vcore/TOC.yml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -99,7 +99,7 @@
9999
- name: Monitor
100100
items:
101101
- name: Monitor metrics
102-
href: request-metrics.md
102+
href: monitor-metrics.md
103103
- name: Monitor diagnostics logs
104104
href: how-to-monitor-diagnostics-logs.md
105105
- name: Use Azure Private Link

articles/cosmos-db/mongodb/vcore/index.yml

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -58,8 +58,6 @@ landingContent:
5858
url: how-to-restore-cluster.md
5959
- text: Monitor diagnostics logs
6060
url: how-to-monitor-diagnostics-logs.md
61-
- text: Request metrics
62-
url: request-metrics.md
6361
- linkListType: concept
6462
links:
6563
- text: MongoDB feature support
90.1 KB
Loading

articles/cosmos-db/mongodb/vcore/request-metrics.md renamed to articles/cosmos-db/mongodb/vcore/monitor-metrics.md

Lines changed: 17 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -23,11 +23,23 @@ It delivers:
2323
* **Drill-down analysis** of a particular Azure Cosmos DB resource. You can diagnose issues or perform detailed analysis by using the categories of utilization, failures, capacity, and operations. Selecting any one of the options provides an in-depth view of the relevant Azure Cosmos DB metrics.
2424
* **Customizable** experience built on top of Azure Monitor workbook templates. You can change what metrics are displayed, modify or set thresholds that align with your limits, and then save into a custom workbook. Charts in the workbooks can then be pinned to Azure dashboards.
2525

26+
## Metrics available today
27+
### System Metrics (available on all cluster tiers)
28+
1. **Committed memory percent**: Shows the percentage of the committed memory limit that is allocated by applications on a node. This metric helps in monitoring the memory usage against the allocated limit.
29+
1. **CPU percent**: Indicates the CPU utilization on a node.
30+
1. **Memory percent**: Shows the memory utilization on a node.
31+
1. **Storage percent:** Displays the available storage percentage on a node.
32+
1. **Storage used**: Represents the actual amount of storage used on a node. This metric is crucial for understanding the storage consumption trends and managing storage resources.
33+
1. **IOPS:** Measures the disk IO operations per second on a node. It provides insights into the read and write performance of the storage system, helping to optimize disk usage.
34+
35+
### Database Metrics
36+
1. **Mongo request duration**: Captures the end-to-end duration in milliseconds of client MongoDB requests handled by the Mongo cluster, updated every 60 seconds. This metric is vital for assessing the responsiveness and latency of the database operations.
37+
2638
>[!NOTE]
27-
>There's no charge to access this feature. However, you'll have to be on the M40 cluster tier or higher to access the metrics. For more information on upgrading, please refer to [this guide](./how-to-scale-cluster.md).
39+
>There's no charge to access Database metrics. However, you'll have to be on the M40 cluster tier or higher to access the metrics. For more information on upgrading, please refer to [this guide](./how-to-scale-cluster.md).
2840
2941

30-
## View the total memory usage metric
42+
## View Metrics
3143

3244
1. Sign in to the [Azure portal](https://portal.azure.com).
3345

@@ -37,11 +49,11 @@ It delivers:
3749

3850
:::image type="content" source="./media/monitor/monitor-metrics-blade.png" alt-text="Metrics blade in Azure Cosmos DB":::
3951

40-
1. Next select the **Memory percent** metric from the list of available metrics. In this example, let's select **Memory percent** and **Avg** as the aggregation value. In addition to these details, you can also select the **Time range** and **Time granularity** of the metrics. At max, you can view metrics for the past 30 days. After you apply the filter, a chart is displayed based on your filter. You can see the average number of request units consumed per minute for the selected period.
52+
1. Next select the **Monogo request duration** metric from the list of available metrics. In this example, let's select **Mongo request duration** and **Avg** as the aggregation value. In addition to these details, you can also select the **Time range** and **Time granularity** of the metrics. At max, you can view metrics for the past 30 days. After you apply the filter, a chart is displayed based on your filter. You can see the average number of request units consumed per minute for the selected period.
4153

42-
:::image type="content" source="./media/monitor/monitor-metric-memory-percent.png" alt-text="Choose a metric from the Azure portal" border="true":::
54+
:::image type="content" source="./media/monitor/monitor-metric-mongo-request-duration.png" alt-text="Choose a metric from the Azure portal" border="true":::
4355

44-
## Filters for memory request duration
56+
## Filters for Database metrics
4557

4658
1. You can also filter metrics and get the charts displayed by a specific **CollectionName**, **DatabaseName**, **Operation**, and **StatusCode**. The **Add filter** and **Apply splitting** options allows you to filter the usage and group the metrics.
4759

0 commit comments

Comments
 (0)