Azure Container Apps Metrics Reference¶
Quick lookup for the platform metrics that Azure Container Apps publishes to Azure Monitor. Use this page when you build alerts, dashboards, autoscaling rules, or KQL queries against your Container Apps.
Two metric namespaces
Container App resources publish metrics under Microsoft.App/containerapps. The Container Apps Environment publishes a separate small set under Microsoft.App/managedEnvironments. Pick the namespace that matches the resource scope you opened in Portal or the resource ID you pass to az monitor metrics list.
Percentage metrics are denominator-relative
CpuPercentage and MemoryPercentage are computed against the container's configured CPU and memory limits, not against the node or environment. A replica scoped to cpu=0.5, memory=1Gi reports 100% when it consumes 0.5 vCPU or 1 GiB respectively. See Percentage metric denominators for details.
Prerequisites¶
- A deployed Container App with a Log Analytics workspace attached to the environment.
- Access to the Container App's resource scope in the Azure Portal, or
az monitor metrics listpermissions on the resource. - Familiarity with revisions and replicas; see Revisions and replicas.
Metric collection flow¶
flowchart TD
A[Container replica] --> B[Container Apps data plane]
B --> C[Azure Monitor metrics pipeline]
C --> D[Microsoft.App/containerapps namespace]
C --> E[Microsoft.App/managedEnvironments namespace]
D --> F[Portal Metrics blade]
D --> G[az monitor metrics list]
D --> H[Alerts and autoscale rules] Quick navigation¶
| Topic | Use when | Page |
|---|---|---|
| Container App metrics | app-level CPU, memory, requests, replicas, restarts | Container App Metrics |
| Environment metrics | environment-level node, ingress, quota | Environment Metrics |
| Percentage metrics | CpuPercentage/MemoryPercentage denominator | Percentage Metrics |
| Dimensions | Portal display name vs API filter key | Dimensions |
| KEDA observability | scale-out troubleshooting | KEDA Observability |
| Evidence and captures | screenshots, lab environment, CLI queries | Evidence |
When to use which metric¶
| Question | Metric(s) | Aggregation |
|---|---|---|
| Is a replica close to its CPU limit? | CpuPercentage | Avg, Max |
| Is a replica close to its memory limit? | MemoryPercentage | Avg, Max |
| What is the absolute CPU consumption? | UsageNanoCores | Avg |
| What is the absolute memory working set? | WorkingSetBytes | Avg |
| How many replicas are running for a revision? | Replicas | Avg, Min, Max |
| Are replicas restarting? | RestartCount | Max, Total |
| What is the request rate and HTTP error split? | Requests | Total, with statusCodeCategory split |
| Are retries or ejections happening? | ResiliencyRequestRetries, ResiliencyEjectedHosts, ResiliencyEjectionsAborted | Total, Max |
| Am I approaching the per-app cores reservation? | TotalCoresQuotaUsed | Max |
| Am I approaching the environment-level cores quota? | Use az containerapp env list-usages (not a metric) | n/a |
See Also¶
- CLI Reference
- Platform Limits
- Environment Variables
- Operations — Monitoring
- Platform — CPU and memory scaler
- KEDA scaler observability
- Troubleshooting — KEDA scaler metrics KQL pack
- Troubleshooting — Scaling events KQL pack
- Troubleshooting — Memory percentage vs. KEDA utilization
- Troubleshooting — HTTP scaling not triggering
Sources¶
- Supported metrics for Microsoft.App/containerapps (Microsoft Learn)
- Supported metrics for Microsoft.App/managedEnvironments (Microsoft Learn)
- Azure Monitor metrics overview (Microsoft Learn)
- Service-to-service connectivity and resiliency in Azure Container Apps (Microsoft Learn)
- Workload profiles in Consumption + Dedicated plan structure (Microsoft Learn)
az monitor metrics listreference (Microsoft Learn)