Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
This article is a list of platform, or automatically collected metrics currently available in Azure Monitor. To query for and access the list of metrics programmatically, use the 2018-01-01 api-version. Other metrics not in this list might be available in the portal or through legacy APIs.
The metrics are organized by resource provider and resource type. For a list of services and the resource providers and types that belong to them, see Resource providers for Azure services.
Exporting platform metrics to other locations
You can export the platform metrics from the Azure monitor using the following methods:
Both metrics export via DCRs and diagnostic settings export metrics to the following locations:
- Azure Storage Accounts.
- Log Analytics workspaces.
- Event Hubs, allowing you to further export to non-Microsoft systems.
Using diagnostic settings is the easiest way to route the metrics, but there are some limitations:
Exportability. All metrics are exportable through the REST API, but some can't be exported through diagnostic settings because of intricacies in the Azure Monitor backend. The column "Exportable via Diagnostic Settings" in the following tables lists which metrics can be exported in this way.
Multi-dimensional metrics. Sending multi-dimensional metrics to other locations is supported by metrics export via data collection rules (DCRs). Exporting multiple dimensions via diagnostic settings isn't supported. Metrics with dimensions are exported by diagnostic settings as flattened single-dimensional metrics, aggregated across dimension values. For example, the Incoming Messages metric on an event hub can be explored and charted on a per-queue level. But when the metric is exported via diagnostic settings, it's represented as all incoming messages across all queues in the event hub.
Guest OS and host OS metrics
Metrics for the guest operating system (guest OS) that runs in Azure Virtual Machines, Service Fabric, and Cloud Services are not listed here. Guest OS metrics must be collected through the Azure Monitor Agent that runs on or as part of the guest operating system. Guest OS metrics include performance counters that track guest CPU percentage or memory usage, both of which are frequently used for autoscaling or alerting. For a list of guest OS metrics, see Virtual machine guest performance counters.
Host OS metrics are available and listed in the tables. Host OS metrics relate to the Hyper-V session that's hosting your guest OS session.
Tip
A best practice is to use and configure the Azure Monitor agent to send guest OS performance metrics into the same Azure Monitor metric database where platform metrics are stored. The agent routes guest OS metrics through the custom metrics API. You can then chart, alert, and otherwise use guest OS metrics like platform metrics.
Alternatively or in addition, you can send the guest OS metrics to Azure Monitor Logs by using the same agent. There you can query on those metrics in combination with non-metric data by using Log Analytics. Standard Log Analytics workspace costs would then apply.
The Azure Monitor agent replaces the Azure Diagnostics extension and Logs Analytics agent, which were previously used for guest OS routing. For important additional information, see Overview of Azure Monitor agents.
Supported metrics and log categories by resource type
Following table lists metrics and log categories available for each resource type.
