Monitor Azure Monitor workspace metrics ingestion

2025-10-13

Prometheus metrics are ingested into an Azure Monitor workspace. Azure monitor workspaces have default limits and quotas for ingestion. When you reach the ingestion limits, throttling can occur. In order to avoid throttling, you can monitor and alert on the workspace ingestion limits.

For more information on Prometheus and Azure Monitor workspace limits and quotas, see Azure Monitor service limits.

View limits and set up recommended alerts

Azure Monitor Workspace exposes a set of metrics that provide insight into ingestion limits and utilization. In the Azure portal, navigate to your Azure Monitor workspace and select Metrics under the Monitoring section.

In the Select metric dropdown, select View standard metrics with the builder.
In the Add metric dropdown, select Add with builder.
In the Metric drop-down, select Active Time Series % Utilization and Events Per Minute Received % Utilization and verify that they are below 100%.

You can set up recommended alerts for Azure Monitor Workspace to monitor the ingestion limits, you can either enable recommended out-of-the-box alerts rules, or manually create new alert rules. The following alerts get created when you set up recommended alerts for the Azure Monitor Workspace.

Alert name	Description	Default threshold	Timeframe (minutes)
AMW Is Approaching Event Ingestion Limit	The Events per min Ingestion utilization is above 75% of the current limit	>75%	5
AMW Is Approaching Active TimeSeries Ingestion Limit	The TimeSeries Ingestion utilization is above 75% of the current limit.	>75%	5
AMW Is At High Risk Of Exceeding Event Ingestion Limit	The Events per min Ingestion utilization is above 95% of the current limit, and is at risk of getting throttled. Request for an increase here	>95%	5
AMW Is At High Risk Of Exceeding Active TimeSeries Ingestion Limit	The TimeSeries Ingestion utilization is above 95% of the current limit, and is at risk of getting throttled. Request for an increase here	>95%	5

Azure portal
Resource Manager

To enable the recommended alert rules, navigate to the Azure Monitor Workspace in Azure portal.

In the Monitoring section, select Alerts > Set up recommended alerts. The Set up recommended alert rules pane opens with a list of recommended alert rules for your Azure Monitor workspace.
In the Select Alert rules section, select all of the rules you want to enable.
In the Notify me by section, select the way you want to be notified if an alert is triggered.
Select Use an existing action group, and enter the details of the existing action group if you want to use an action group that already exists.
Select Save.

To enable the recommended alert rules, use the following Resource Manager template and parameters files with any of the standard deployment options.

Template File:

{
    "$schema": "https://schema.management.azure.com/schemas/2019-04-01/deploymentTemplate.json#",
    "contentVersion": "1.0.0.0",
    "parameters": {
        "actionGroupResourceId": {
            "type": "string",
            "metadata": {
                "description": "Action Group ResourceId"
            }
        },
        "azureMonitorWorkspaceResourceId": {
            "type": "string",
            "metadata": {
                "description": "ResourceId of Azure Monitor Workspace (AMW) to associate to"
            }
        }
    },
    "variables": {
        "amwName": "[last(split(parameters('azureMonitorWorkspaceResourceId'), '/'))]"
    },
    "resources": [
        {
            "name": "[concat('AMW Is Approaching Event Ingestion Limit - ', variables('amwName'))]",
            "type": "Microsoft.Insights/metricAlerts",
            "apiVersion": "2018-03-01",
            "___location": "global",
            "tags": {
                "alertRuleCreatedWithAlertsRecommendations": "true"
            },
            "properties": 
            {
                "description": "AMW Is Approaching Event Ingestion Limit - Request for an increase https://go.microsoft.com/fwlink/?linkid=2270124",
                "severity": 3,
                "enabled": true,
                "scopes": [
                    "[parameters('azureMonitorWorkspaceResourceId')]"
                ],
                "evaluationFrequency": "PT5M",
                "windowSize": "PT30M",
                "criteria": {
                    "allOf": [
                    {
                        "threshold": 75,
                        "name": "EventsCriteria",
                        "metricName": "EventsPerMinuteIngestedPercentUtilization",
                        "operator": "GreaterThan",
                        "timeAggregation": "Average",
                        "criterionType": "StaticThresholdCriterion"
                    }
                ],
                "odata.type": "Microsoft.Azure.Monitor.MultipleResourceMultipleMetricCriteria"
                },
                "actions": [
                {
                    "actionGroupId": "[parameters('actionGroupResourceId')]"
                }
            ]
        }
    },
    {
            "name": "[concat('AMW Is Approaching Active TimeSeries Ingestion Limit - ', variables('amwName'))]",
            "type": "Microsoft.Insights/metricAlerts",
            "apiVersion": "2018-03-01",
            "___location": "global",
            "tags": {
                "alertRuleCreatedWithAlertsRecommendations": "true"
            },
            "properties": 
            {
                "description": "AMW Is Approaching Active Timeseries Limit - Request for an increase https://go.microsoft.com/fwlink/?linkid=2270124",
                "severity": 3,
                "enabled": true,
                "scopes": [
                    "[parameters('azureMonitorWorkspaceResourceId')]"
                ],
                "evaluationFrequency": "PT5M",
                "windowSize": "PT30M",
                "criteria": {
                    "allOf": [
                    {
                        "threshold": 85,
                        "name": "TimeSeriesCriteria",
                        "metricName": "ActiveTimeSeriesPercentUtilization",
                        "operator": "GreaterThan",
                        "timeAggregation": "Average",
                        "criterionType": "StaticThresholdCriterion"
                    }
                ],
                "odata.type": "Microsoft.Azure.Monitor.MultipleResourceMultipleMetricCriteria"
                },
                "actions": [
                {
                    "actionGroupId": "[parameters('actionGroupResourceId')]"
                }
            ]
        }
    },
    {
            "name": "[concat('AMW Is At High Risk Of Exceeding Event Ingestion Limit - ', variables('amwName'))]",
            "type": "Microsoft.Insights/metricAlerts",
            "apiVersion": "2018-03-01",
            "___location": "global",
            "tags": {
                "alertRuleCreatedWithAlertsRecommendations": "true"
            },
            "properties": 
            {
                "description": "AMW Is At High Risk Of Exceeding Event Ingestion Limit - Request for an increase https://go.microsoft.com/fwlink/?linkid=2270124",
                "severity": 2,
                "enabled": true,
                "scopes": [
                    "[parameters('azureMonitorWorkspaceResourceId')]"
                ],
                "evaluationFrequency": "PT5M",
                "windowSize": "PT30M",
                "criteria": {
                    "allOf": [
                    {
                        "threshold": 95,
                        "name": "EventsCriteria",
                        "metricName": "EventsPerMinuteIngestedPercentUtilization",
                        "operator": "GreaterThan",
                        "timeAggregation": "Average",
                        "criterionType": "StaticThresholdCriterion"
                    }
                ],
                "odata.type": "Microsoft.Azure.Monitor.MultipleResourceMultipleMetricCriteria"
                },
                "actions": [
                {
                    "actionGroupId": "[parameters('actionGroupResourceId')]"
                }
            ]
        }
    },
        {
            "name": "[concat('AMW Is At High Risk Of Exceeding Active TimeSeries Ingestion Limit - ', variables('amwName'))]",
            "type": "Microsoft.Insights/metricAlerts",
            "apiVersion": "2018-03-01",
            "___location": "global",
            "tags": {
                "alertRuleCreatedWithAlertsRecommendations": "true"
            },
            "properties": 
            {
                "description": "AMW Is At High Risk Of Exceeding Active TimeSeries Limit - Request for an increase https://go.microsoft.com/fwlink/?linkid=2270124",
                "severity": 2,
                "enabled": true,
                "scopes": [
                    "[parameters('azureMonitorWorkspaceResourceId')]"
                ],
                "evaluationFrequency": "PT5M",
                "windowSize": "PT30M",
                "criteria": {
                    "allOf": [
                    {
                        "threshold": 95,
                        "name": "TimeSeriesCriteria",
                        "metricName": "ActiveTimeSeriesPercentUtilization",
                        "operator": "GreaterThan",
                        "timeAggregation": "Average",
                        "criterionType": "StaticThresholdCriterion"
                    }
                ],
                "odata.type": "Microsoft.Azure.Monitor.MultipleResourceMultipleMetricCriteria"
                },
                "actions": [
                {
                    "actionGroupId": "[parameters('actionGroupResourceId')]"
                }
            ]
        }
    }
  ]
}

Parameter file: Update the Parameters.json file with the Resource Id of the Azure Monitor Workspace and the Resource ID of the Action Group

{
  "$schema": "https://schema.management.azure.com/schemas/2019-04-01/deploymentParameters.json#",
  "contentVersion": "1.0.0.0",
  "parameters": {
    "azureMonitorWorkspaceResourceId": {
      "value": "<<ResourceID of the Azure Monitor Workspace>>"
    },
    "actionGroupResourceId": {
      "value": "<<ResourceID of the Action Group>>"
    }
  }
}

Run the below commands to execute the Resource Manager template deployment:

For Azure CLI:

az login
az account set --subscription <subscriptionId>
az deployment group create --name AMWRecAlerts --resource-group <resourceGroupName> --template-file <<template-file-as-above.json>> --parameters <<parameter-file-from-above.json>>

For Azure PowerShell:

Connect-AzAccount
New-AzResourceGroupDeployment -Name AMWRecAlerts -ResourceGroupName  <resourceGroupName> -TemplateFile <<template-file-as-above.json>> -TemplateParameterFile <<parameter-file-from-above.json>>

Request for an increase in ingestion limits (Preview)

Request for an increase in ingestion limits using Azure Resource Manager API. This API is in Preview and below conditions apply with this API:

Request for an increase in limit from the default 1 Million events/min or active Timeseries to up to 20 Million events/min or active Timeseries with an API update through cli or through ARM update. For limits above 20 Million, create a support ticket.
- For limit increase request up to 2 Million, request is autoapproved.
- For limit increase request above 2 Million, current ingestion usage should be at 50% of desired limit, that is, if the current limit is 5 Million, they can request for increase upto 10 Million. You can request up to 20 Million.
- For requests beyond 20 Million, create a support ticket.
Creation of an Azure Monitor Workspace always applies the default limits. Creating an Azure Monitor Workspace with custom limits is not supported.

This document explains how to use the ARM API to update the data ingestion limits of your Azure Monitor Workspaces.

Prerequisites

A command-line tool to run the ARM template commands, such as Azure PowerShell, or Azure CLI

Step 1: Download the ARM templates and update the parameters

Download the ARM template files (AMWLimitIncrease-Template.json and AMWLimitIncrease-Parameters.json and update the Parameters.json file with the subscription id, name of the resource group where the AMW is in, Name of the AMW, ___location of the AMW, and required ingestion limits (maximum is 20000000).

Step 2: Execute the ARM update

Run the below commands from the downloaded ARM templates folder:

For Azure CLI:

az login
az account set --subscription <subscriptionId>
az deployment group create --name AmwLimits --resource-group <resourceGroupName> --template-file AMWLimitIncrease-Template.json --parameters AMWLimitIncrease-Parameters.json

For Azure PowerShell:

Connect-AzAccount
New-AzResourceGroupDeployment -Name AmwLimits -ResourceGroupName  <resourceGroupName> -TemplateFile AMWLimitIncrease-Template.json -TemplateParameterFile AMWLimitIncrease-Parameters.json

Step 3: Verify if the limits are updated

To verify if the limits are updated successfully, you can go to the Azure portal, navigate to the Azure Monitor Workspace -> Metrics explorer -> In the Metric dropdown, select "View standard metrics with the builder", and then verify if the updated limits are applied to the "Active Time Series Limit" and "Events per minute Ingested Limit".

Troubleshoot issues with increasing ingestion limits using ARM API

If you see an error when using the API to request for a limit increase, check the error response to find the cause of the error.

Requested limit is above 20 Million: "ActiveTimeSeries quota requested exceeds the maximum limit of {MaxAutoApprovedActiveTimeSeries}": This error occurs when you request for a limit of 20 Million or more events/min or Active Timeseries. Currently the API only supports an increase up to 20M. You can request for more ingestion limit by creating a support ticket.
Usage is less compared to requested limit: The current utilization does not meet the criteria for MaxTimeSeries quota requested. This error occurs when your current ingestion is less than 50% of the requested limit. Reach the required usage threshold of 50% of desired limit before requesting an increase, or request a limit increase of up to 200% of your current usage. To check the current usage, go to the Azure portal, navigate to the Azure Monitor Workspace -> Metrics explorer -> In the Metric dropdown, select "View standard metrics with the builder," and then select "Active Time Series % Utilization" and "Events per minute received % Utilization".

Request for an increase in ingestion limits through support ticket

To open a support ticket:

Select Support + Troubleshooting from the left pane of the Azure portal.
Enter Service and subscription limits (quotas) in the search field and select Go.
Select Service and subscription limits (quotas), select Next, then select Create a new support request.
Select your subscription and then select Managed Prometheus as the Quota type.
Complete the requested details and submit the request.

Query and alert on workspace ingestion metrics

To query Azure Monitor workspace metrics to monitor the ingestion limits, use the following steps:

In the Azure portal, navigate to your Azure Monitor workspace and select Metrics under the Monitoring section.
In the Add metric dropdown, select Add with builder.
Select the Azure Monitor workspace as scope.
Select Standard metrics for the Metric Namespace.
In the Metric drop-down, select Active Time Series % Utilization and Events Per Minute Received % Utilization and verify that they are below 100%.
Select New alert rule to create an Azure alert. Set an Azure Alert to monitor the utilization and fire an alert when the utilization is greater than a certain threshold. For more information, see Create a metric alert for an Azure resource.

See your alerts in the Azure portal by selecting Alerts under the Monitoring section of your Azure Monitor workspace.

The alert is fired if the ingestion utilization is more than the threshold. Request an increase in the limit by creating a support ticket.

Next steps

Feedback

Was this page helpful?