Skip to content

Commit d40f635

Browse files
committed
Merge branch 'sunasing-br-1013' of https://github.com/sunasing/azure-docs-pr into sunasing-br-1013
updating images
2 parents a7c4dd7 + e591dc7 commit d40f635

File tree

1 file changed

+12
-7
lines changed

1 file changed

+12
-7
lines changed

articles/azure-monitor/essentials/prometheus-metrics-overview.md

Lines changed: 12 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -111,23 +111,28 @@ If you use the Azure portal to enable Prometheus metrics collection and install
111111
Azure Monitor Managed service for Prometheus has default limits and quotas for ingestion. For information on Prometheus metrics limits, see [Azure Monitor service limits](../service-limits.md#prometheus-metrics). When you reach the ingestion limits throttling can occur. In order to avoid throttling, you can monitor and setup an alert on Azure Monitor Workspace ingestion limits.
112112

113113
1. In the Azure portal, navigate to your Azure Monitor Workspace, click on **Metrics** under the **Monitoring** section.
114-
1. Select the AMW as scope, and in the drop-down for Metric, select *"View standard metrics with the builder"*.
115-
1. In the drop-down for Metric, select **Active Time Series % Utilization** and **Events Per Minute Ingested % Utilization** and verify that they are below 100%.
114+
2. Select the AMW as scope, and in the drop-down for Metric, select *"View standard metrics with the builder"*.
115+
3. In the drop-down for Metric, select **Active Time Series % Utilization** and **Events Per Minute Ingested % Utilization** and verify that they are below 100%.
116+
116117
:::image type="content" source="media/azure-monitor-workspace-overview/amw-limits-metrics.png" alt-text="Screenshot that shows how to create an alert rule for AMW ingestion limits":::
117-
1. You can set an Azure Alert to monitor the utilization and fire an alert when the utilization is greater than a certain threshold (eg. 80% of the limit). Click on "**New alert rule**" to create an Azure alert for the same.
118+
119+
4. You can set an Azure Alert to monitor the utilization and fire an alert when the utilization is greater than a certain threshold (eg. 80% of the limit). Click on "**New alert rule**" to create an Azure alert for the same.
120+
118121
:::image type="content" source="media/azure-monitor-workspace-overview/alert-amw-limit.png" alt-text="Screenshot that shows how to create an alert for AMW limits.":::
119122

120123
If the alert is fired i.e. the ingestion utilization is more than the threshold, you can request an increase in these limits by creating a support ticket.
121124

122125
1. In the Azure portal, navigate to your Azure Monitor Workspace, click on **Support + Troubleshooting**.
123-
1. Type the issue eg. "Service and subscription limits (quotas)", then select **Service and subscription limits (quotas)** and click "Next".
126+
2. Type the issue eg. "Service and subscription limits (quotas)", then select **Service and subscription limits (quotas)** and click "Next".
127+
124128
:::image type="content" source="media/azure-monitor-workspace-overview/amw-support-ticket.png" alt-text="Screenshot that shows how to create a support ticket for limit increase.":::
125-
1. In the next screen, select your subscription and then select **Managed Prometheus** as the **Quota type**.
126-
1. Provide additional details to create the support ticket.
129+
130+
3. In the next screen, select your subscription and then select **Managed Prometheus** as the **Quota type**.
131+
4. Provide additional details to create the support ticket.
127132

128133

129134
## Next steps
130135

131136
- [Enable Azure Monitor managed service for Prometheus on your Kubernetes clusters](../containers/kubernetes-monitoring-enable.md).
132137
- [Configure Prometheus alerting and recording rules groups](prometheus-rule-groups.md).
133-
- [Customize scraping of Prometheus metrics](prometheus-metrics-scrape-configuration.md).
138+
- [Customize scraping of Prometheus metrics](prometheus-metrics-scrape-configuration.md).

0 commit comments

Comments
 (0)