Azure Monitor CPU and Memory Percentage metrics stopped reporting for App Service Plan

Suresh Panthangi 21 Reputation points
2026-09-11T05:21:59.6033333+00:00

The issue reproduces directly in Azure Portal Metrics Explorer and through the Azure Monitor CLI/API.

For the affected S3 Linux App Service Plan, both CPU Percentage (Average) and Memory Percentage (Average) show -- with no datapoints, even with Last 1 hour / 1-minute granularity.

At the same time, Data In returns 0 B, demonstrating that Azure Monitor is responding for the resource and other metrics are available.

The App Service Plan is healthy and in Ready/Running state with one Large worker, and the applications attached to it are running.

A comparable S3 Linux App Service Plan reports CPU and Memory metrics normally.

Please help why the underlying Azure App Service platform is no longer emitting CPU Percentage and Memory Percentage datapoints for this specific App Service Plan, and advise on a remediation that does not require recreating or unnecessarily modifying the production App Service Plan.

Azure Monitor
Azure Monitor

An Azure service that is used to collect, analyze, and act on telemetry data from Azure and on-premises environments.

0 comments

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Allan Solomon Mejia 9,000 Reputation points
    2026-09-12T02:48:05.54+00:00

    Hello @Suresh Panthangi

    Based on what you've described, this looks more like a platform-side metric emission issue for that specific App Service Plan/worker than an Azure Monitor query or visualization problem.

    CpuPercentage and MemoryPercentage are supported platform metrics for Microsoft.Web/serverfarms, with 1-minute (PT1M) granularity. Both are automatically collected App Service Plan metrics.

    The fact that both metrics stopped at the same time, the same gap appears in Metrics Explorer and through CLI/API, Data In continues returning data points, the plan remains Ready/Running, and another comparable S3 Linux plan reports normally strongly suggests the problem is upstream of Azure Monitor. The affected worker/plan is no longer publishing those two resource-utilization counters correctly.

    First, check the Activity Log around the exact time the metrics stopped for any platform maintenance, worker change, scale operation, deployment, or configuration event. Also check App Service > Diagnose and solve problems for platform or availability events.

    Since you specifically want to avoid recreating or unnecessarily modifying the production plan, I don't recommend scaling or moving the workload just to restore telemetry at this stage.

    If CpuPercentage and MemoryPercentage continue returning no data points while other plan metrics remain available, open an Azure Support request under App Service and provide the resource ID, region, SKU, exact UTC timestamp when emission stopped, and CLI/API output showing the missing data points. Ask support to investigate the App Service platform metric-emission pipeline/worker telemetry for the serverfarm.

    This distinction is important: Azure Monitor can't display a value that the App Service resource provider isn't emitting. The continued availability of other metrics makes a general Azure Monitor outage or resource-health failure less likely.

    References:

    Supported metrics for Microsoft.Web/serverfarms

    Azure App Service quotas and metrics

    Hope this helps isolate where the issue is occurring.

    =============================================================================

    Help make this community better for everyone: If this answer helped or resolved your issue, please accept it or upvote it. If not, share more details in a comment so we can continue the discussion and find the right solution.

    Was this answer helpful?

    0 comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.