You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
description: This article covers important reference material for monitoring Azure virtual machines.
4
-
ms.service: virtual-machines
5
-
ms.custom: subject-monitoring
6
-
ms.date: 12/03/2022
2
+
title: Monitoring data reference for Azure Virtual Machines
3
+
description: This article contains important reference material you need when you monitor Azure Virtual Machines and Virtual Machine Scale Sets.
4
+
ms.date: 02/20/2024
5
+
ms.custom: horz-monitor
7
6
ms.topic: reference
7
+
ms.service: virtual-machines
8
8
---
9
9
10
-
# Reference: Monitoring Azure virtual machine data
11
-
12
-
For more information about collecting and analyzing monitoring data for Azure virtual machines (VMs), see [Monitoring Azure virtual machines](monitor-vm.md).
13
-
14
-
## Metrics
15
-
16
-
This section lists the platform metrics that are collected for Azure virtual machines and Virtual Machine Scale Sets.
17
-
18
-
| Metric type | Resource provider / type namespace<br/> and link to individual metrics |
| Virtual Machine Scale Sets and virtual machines |[Microsoft.Compute/virtualMachineScaleSets/virtualMachines](../azure-monitor/essentials/metrics-supported.md#microsoftcomputevirtualmachinescalesetsvirtualmachines)|
23
-
24
-
For more information, see a list of [platform metrics that are supported in Azure Monitor](/azure/azure-monitor/platform/metrics-supported).
25
-
26
-
## Metric dimensions
27
-
28
-
For more information about metric dimensions, see [Multi-dimensional metrics](../azure-monitor/essentials/data-platform-metrics.md#multi-dimensional-metrics).
29
-
30
-
Azure virtual machines and Virtual Machine Scale Sets have the following dimensions that are associated with their metrics.
31
-
32
-
| Dimension name | Description |
33
-
| ------------------- | ----------------- |
34
-
| LUN | Logical unit number |
35
-
| VMName | Used with Virtual Machine Scale Sets |
36
-
37
-
## VM availability metric (preview)
10
+
<!--
11
+
IMPORTANT
12
+
To make this template easier to use, first:
13
+
1. Search and replace Virtual Machines with the official name of your service.
14
+
2. Search and replace virtual-machines with the service name to use in GitHub filenames.-->
15
+
16
+
<!-- VERSION 3.0 2024_01_01
17
+
For background about this template, see https://review.learn.microsoft.com/en-us/help/contribute/contribute-monitoring?branch=main -->
18
+
19
+
<!-- Most services can use the following sections unchanged. All headings are required unless otherwise noted.
20
+
The sections use #included text you don't have to maintain, which changes when Azure Monitor functionality changes. Add info into the designated service-specific places if necessary. Remove #includes or template content that aren't relevant to your service.
21
+
22
+
At a minimum your service should have the following two articles:
23
+
24
+
1. The primary monitoring article (based on the template monitor-service-template.md)
25
+
- Title: "Monitor Virtual Machines"
26
+
- TOC title: "Monitor"
27
+
- Filename: "monitor-virtual-machines.md"
28
+
29
+
2. A reference article that lists all the metrics and logs for your service (based on this template).
30
+
- Title: "Virtual Machines monitoring data reference"
See [Monitor Azure Virtual Machines](monitor-virtual-machines.md) for details on the data you can collect for Azure Virtual Machines and Virtual Machine Scale Sets and how to use it.
<!-- Repeat the following section for each resource type/namespace in your service. -->
45
+
46
+
>[!IMPORTANT]
47
+
>Metrics for the guest operating system (guest OS) that runs in Azure Virtual Machines aren't listed here. Guest OS metrics must be collected through one or more agents that run 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.
48
+
>
49
+
>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. For more information, see [Guest OS and host OS metrics](/azure/azure-monitor/reference/supported-metrics/metrics-index#guest-os-and-host-os-metrics).
50
+
51
+
### Supported metrics for Microsoft.Compute/virtualMachines
52
+
The following table lists the metrics available for the Microsoft.Compute/virtualMachines resource type.
53
+
<!-- For each ### section:
54
+
1. Replace the <ResourceType/namespace> placeholder in the heading and introductory sentence. Example: ### Supported metrics for Microsoft.Storage/storageAccounts/blobServices
55
+
2. Find the metrics for the resource type at https://learn.microsoft.com/azure/azure-monitor/reference/supported-metrics/metrics-index#supported-metrics-per-resource-type, which is autogenerated from underlying systems.
56
+
3. Either link to the listed metrics page(s), OR #include the metrics table(s), starting with the tableheader #include.
57
+
4. Add any further information after each metrics table #include or link.
58
+
Example link to metrics page: - [Microsoft.Storage/storageAccounts/blobServices](/azure/azure-monitor/reference/supported-metrics/microsoft-storage-storageaccounts-blobservices-metrics)
59
+
Example #include. Start with the metrics tableheader: -->
The VM availability metric is currently in public preview. This metric value indicates whether a machine is currently running and available. You can use the metric to trend availability over time and to alert if the machine is stopped. VM availability has the values in the following table.
39
75
40
76
| Value | Description |
@@ -43,21 +79,85 @@ The VM availability metric is currently in public preview. This metric value ind
43
79
| 0 | VM is unavailable. The VM could be stopped or rebooting. If you shutdown a VM from within the VM, it will emit this value. |
44
80
| Null | State of the VM is unknown. If you stop a VM from the Azure portal, CLI, or PowerShell, it will immediately stop emitting the availability metric, and you will see null values. |
<!-- Use one of the following includes, depending on whether you have metrics with dimensions.
85
+
- If you have metrics with dimensions, use the following include and list the metrics with dimensions after the include. For an example, see https://learn.microsoft.com/azure/storage/common/monitor-storage-reference#metrics-dimensions. Questions: email [email protected]. -->
This section refers to all the Azure Monitor Logs tables that are relevant to virtual machines and Virtual Machine Scale Sets and available for query by Log Analytics.
Virtual Machines and Virtual Machine Scale Sets have the following dimensions that are associated with their metrics:
55
89
56
-
For reference documentation about Azure Monitor Logs and Log Analytics tables, see the [Azure Monitor Logs table reference](/azure/azure-monitor/reference/tables/tables-resourcetype).
57
-
58
-
## Activity log
90
+
| Dimension name | Description |
91
+
| ------------------- | ----------------- |
92
+
| LUN | Logical unit number |
93
+
| VMName | Used with Virtual Machine Scale Sets |
59
94
60
-
The following table lists a few example operations that relate to creating virtual machines in the activity log. For a complete list of possible log entries, see [Microsoft.Compute Resource Provider options](../role-based-access-control/resource-provider-operations.md#compute).
95
+
<!-- If you DON'T have metrics with dimensions, use the following include:
<!-- Add at least one resource provider/resource type here. Repeat this section for each resource type/namespace in your service. Example: ### Supported resource logs for Microsoft.Storage/storageAccounts/blobServices -->
102
+
### Supported resource logs for Microsoft.Compute/virtualMachines
Find the table(s) for your service at https://learn.microsoft.com/azure/azure-monitor/reference/tables/tables-resourcetype. These files are auto generated from the REST API.
149
+
Also refer to https://learn.microsoft.com/azure/azure-monitor/reference/tables/azurediagnostics#azure-diagnostics-mode to see whether your service uses the AzureDiagnostics table in Azure Monitor Logs / Log Analytics.
150
+
Link to the service-specific tables. If your service uses the AzureDiagnostics table, list the fields you use and what they're for. If your service uses both tables, list both types of information. Add any further information after each table link, such as descriptions and usage, or information not found in the tables.
151
+
152
+
IMPORTANT: Field names for Log Analytics may vary from the same field names for Storage. Many services need a mapping table to map the two sets of fields. -->
<!-- Refer to https://learn.microsoft.com/azure/role-based-access-control/resource-provider-operations and link to the possible operations for your service, using the format - [<Namespace> resource provider operations](/azure/role-based-access-control/resource-provider-operations#<namespace>).
If there are other operations not in the link, list them here in table form. -->
159
+
160
+
The following table lists a few example operations that relate to creating VMs in the activity log. For a complete list of operations, see [Microsoft.Compute resource provider operations](/azure/role-based-access-control/resource-provider-operations#microsoftcompute).
61
161
62
162
| Operation | Description |
63
163
|:---|:---|
@@ -68,9 +168,11 @@ The following table lists a few example operations that relate to creating virtu
68
168
| Microsoft.Compute/virtualMachines/extensions/write | Creates a new virtual machine extension or updates an existing one |
69
169
| Microsoft.Compute/virtualMachineScaleSets/write | Starts the instances of the virtual machine scale set |
70
170
71
-
For more information about the schema of activity log entries, see [Activity log schema](../azure-monitor/essentials/activity-log-schema.md).
72
-
171
+
<!-- ## Other schemas. Optional section. Please keep heading in this order. If your service uses other schemas, add the following include and information.
List other schemas and their usage here. These can be resource logs, alerts, event hub formats, etc. depending on what you think is important. You can put JSON messages, API responses not listed in the REST API docs, and other similar types of info here. -->
73
174
74
-
## See also
175
+
## Related content
75
176
76
-
For a description of monitoring Azure virtual machines, see [Monitoring Azure virtual machines](../virtual-machines/monitor-vm.md).
177
+
- See [Monitor Virtual Machines](monitor-virtual-machines.md) for a description of monitoring Virtual Machines.
178
+
- See [Monitor Azure resources with Azure Monitor](/azure/azure-monitor/essentials/monitor-azure-resource) for details on monitoring Azure resources.
0 commit comments