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
Copy file name to clipboardExpand all lines: articles/azure-monitor/vm/vminsights-enable-powershell.md
+8-8Lines changed: 8 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,6 @@
1
1
---
2
2
title: Enable VM insights using PowerShell
3
-
description: Describes how to enable VM insights for Azure virtual machines or virtual machine scale sets using Azure PowerShell.
3
+
description: Describes how to enable VM insights for Azure virtual machines or Virtual Machine Scale Sets using Azure PowerShell.
4
4
ms.topic: conceptual
5
5
author: bwren
6
6
ms.author: bwren
@@ -12,27 +12,27 @@ ms.date: 06/08/2022
12
12
This article describes how to enable VM insights on Azure virtual machines using PowerShell. This procedure can be used for the following:
13
13
14
14
- Azure virtual machine
15
-
- Azure virtual machine scale set
15
+
- Azure Virtual Machine Scale Set
16
16
17
17
> [!NOTE]
18
18
> This article only applies to the Log Analytics agent. To enable VM insights with the Azure monitor agent, use other installation methods described in [Enable VM insights overview](vminsights-enable-overview.md).
19
19
## Prerequisites
20
20
21
21
-[Log Analytics workspace configured for VM insights](../vm/vminsights-configure-workspace.md).
22
-
- See [Supported operating systems](./vminsights-enable-overview.md#supported-operating-systems) to ensure that the operating system of the virtual machine or virtual machine scale set you're enabling is supported.
22
+
- See [Supported operating systems](./vminsights-enable-overview.md#supported-operating-systems) to ensure that the operating system of the virtual machine or Virtual Machine Scale Set you're enabling is supported.
23
23
- See [Manage the Azure Monitor agent](../agents/azure-monitor-agent-manage.md#prerequisites) for prerequisites related to Azure Monitor agent.
24
24
25
25
## PowerShell script
26
26
27
-
To enable VM insights for multiple VMs or virtual machine scale sets, use the PowerShell script [Install-VMInsights.ps1](https://www.powershellgallery.com/packages/Install-VMInsights), which is available from the Azure PowerShell Gallery. This script iterates through:
27
+
To enable VM insights for multiple VMs or Virtual Machine Scale Sets, use the PowerShell script [Install-VMInsights.ps1](https://www.powershellgallery.com/packages/Install-VMInsights), which is available from the Azure PowerShell Gallery. This script iterates through:
28
28
29
-
- Every virtual machine and virtual machine scale set in your subscription.
29
+
- Every virtual machine and Virtual Machine Scale Set in your subscription.
30
30
- The scoped resource group that's specified by *ResourceGroup*.
31
-
- A single VM or virtual machine scale set that's specified by *Name*.
31
+
- A single VM or Virtual Machine Scale Set that's specified by *Name*.
32
32
33
-
For each virtual machine or virtual machine scale set, the script verifies whether the VM extension for the Log Analytics agent and Dependency agent is already installed. If both extensions are installed, the script tries to reinstall it. If both extensions aren't installed, the script installs them.
33
+
For each virtual machine or Virtual Machine Scale Set, the script verifies whether the VM extension for the Log Analytics agent and Dependency agent is already installed. If both extensions are installed, the script tries to reinstall it. If both extensions aren't installed, the script installs them.
34
34
35
-
Verify you are using Azure PowerShell module Az version 1.0.0 or later with `Enable-AzureRM` compatibility aliases enabled. Run `Get-Module -ListAvailable Az` to find the version. If you need to upgrade, see [Install Azure PowerShell module](/powershell/azure/install-az-ps). If you're running PowerShell locally, you also need to run `Connect-AzAccount` to create a connection with Azure.
35
+
Verify you're using Azure PowerShell module Az version 1.0.0 or later with `Enable-AzureRM` compatibility aliases enabled. Run `Get-Module -ListAvailable Az` to find the version. If you need to upgrade, see [Install Azure PowerShell module](/powershell/azure/install-az-ps). If you're running PowerShell locally, you also need to run `Connect-AzAccount` to create a connection with Azure.
36
36
37
37
To get a list of the script's argument details and example usage, run `Get-Help`.
Copy file name to clipboardExpand all lines: articles/azure-monitor/vm/vminsights-enable-resource-manager.md
+14-14Lines changed: 14 additions & 14 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,6 @@
1
1
---
2
2
title: Enable VM insights using Resource Manager templates
3
-
description: This article describes how you enable VM insights for one or more Azure virtual machines or virtual machine scale sets by using Azure PowerShell or Azure Resource Manager templates.
3
+
description: This article describes how you enable VM insights for one or more Azure virtual machines or Virtual Machine Scale Sets by using Azure PowerShell or Azure Resource Manager templates.
4
4
ms.topic: conceptual
5
5
author: bwren
6
6
ms.author: bwren
@@ -9,21 +9,21 @@ ms.date: 06/08/2022
9
9
---
10
10
11
11
# Enable VM insights using Resource Manager templates
12
-
This article describes how to enable VM insights for a virtual machine or virtual machine scale set using Resource Manager templates. This procedure can be used for the following:
12
+
This article describes how to enable VM insights for a virtual machine or Virtual Machine Scale Set using Resource Manager templates. This procedure can be used for:
13
13
14
-
- Azure virtual machine
15
-
- Azure virtual machine scale set
16
-
- Hybrid virtual machine connected with Azure Arc
14
+
- Azure virtual machines
15
+
- Azure Virtual Machine Scale Sets
16
+
- Hybrid virtual machines connected with Azure Arc
- To enable VM insights for Log Analytics agent, [configure your Log Analytics workspace for VM insights](../vm/vminsights-configure-workspace.md). This prerequisite isn't relevant if you're using Azure Monitor Agent.
22
-
- See [Supported operating systems](./vminsights-enable-overview.md#supported-operating-systems) to ensure that the operating system of the virtual machine or virtual machine scale set you're enabling is supported.
22
+
- See [Supported operating systems](./vminsights-enable-overview.md#supported-operating-systems) to ensure that the operating system of the virtual machine or Virtual Machine Scale Set you're enabling is supported.
23
23
- See [Manage the Azure Monitor agent](../agents/azure-monitor-agent-manage.md#prerequisites) for prerequisites related to Azure Monitor agent.
24
24
25
25
## Resource Manager templates
26
-
Azure Resource Manager templates are available for download that onboard virtual machines and virtual machine scale sets. A different set of templates is used for Azure Monitor agent and Log Analytics agent. The templates install the required agents and perform the configuration required to onboard to machine to VM insights.
26
+
Azure Resource Manager templates are available for download that onboard virtual machines and Virtual Machine Scale Sets. A different set of templates is used for Azure Monitor agent and Log Analytics agent. The templates install the required agents and perform the configuration required to onboard to machine to VM insights.
27
27
28
28
29
29
If you aren't familiar how to deploy a Resource Manager template, see [Deploy templates](#deploy-templates) for different options.
@@ -46,14 +46,14 @@ Use on of the following sets of template and parameter files folders depending o
46
46
47
47
48
48
### Deploy agents to machines
49
-
Once the data collection rule has been created, deploy the agents using one of the templates in the following table. You specify the resource ID of the DCR that you created in the first step in the parameters file. Each of the templates requires that the virtual machine or virtual machine scale set is already created.
49
+
Once the data collection rule has been created, deploy the agents using one of the templates in the following table. You specify the resource ID of the DCR that you created in the first step in the parameters file. Each of the templates requires that the virtual machine or Virtual Machine Scale Set is already created.
50
50
51
51
| Folder | File | Description |
52
52
|:---|:---|
53
53
| ExistingVmOnboarding\\<br>PerfAndMapOnboarding | ExistingVmOnboardingTemplate.json<br>ExistingVmOnboardingParameters.json | Enable both Performance and Map experience for virtual machine. Use with PerfAndMapDcr. |
54
54
| ExistingVmOnboarding\\<br>PerfOnlyOnboarding | ExistingVmOnboardingTemplate.json<br>ExistingVmOnboardingParameters.json | Enable only Performance experience for virtual machine. Use with PerfOnlyDCR. |
55
-
| ExistingVmssOnboarding\\<br>PerfAndMapOnboarding | ExistingVmOnboardingTemplate.json<br>ExistingVmssOnboardingParameters.json | Enable both Performance and Map experience for virtual machine scale set. Use with PerfAndMapDcr. |
56
-
| ExistingVmssOnboarding\\<br>PerfOnlyOnboarding | ExistingVmOnboardingTemplate.json<br>ExistingVmssOnboardingParameters.json | Enable only Performance experience for virtual machine scale set. Use with PerfOnlyDCR. |
55
+
| ExistingVmssOnboarding\\<br>PerfAndMapOnboarding | ExistingVmOnboardingTemplate.json<br>ExistingVmssOnboardingParameters.json | Enable both Performance and Map experience for Virtual Machine Scale Set. Use with PerfAndMapDcr. |
56
+
| ExistingVmssOnboarding\\<br>PerfOnlyOnboarding | ExistingVmOnboardingTemplate.json<br>ExistingVmssOnboardingParameters.json | Enable only Performance experience for Virtual Machine Scale Set. Use with PerfOnlyDCR. |
57
57
58
58
> [!NOTE]
59
59
> If your virtual machines scale sets have an upgrade policy set to manual, VM insights will not be enabled for instances by default after installing the template. You must manually upgrade the instances.
@@ -77,8 +77,8 @@ Once the workspace has been configured, deploy the agents using one of the templ
77
77
|:---|:---|
78
78
| NewVmOnboarding | NewVmOnboardingTemplate.json<br>NewVmOnboardingParameters.json | Creates a virtual machine and enables it to be monitored with VM insights. |
79
79
| ExistingVmOnboarding | ExistingVmOnboarding.json<br>ExistingVmOnboarding.json | Enables VM insights on existing virtual machine. |
80
-
| NewVmssOnboarding | NewVmssOnboarding.json<br>NewVmssOnboarding.json | Creates a virtual machine scale set and enables it to be monitored with VM insights. |
81
-
| ExistingVmssOnboarding | ExistingVmssOnboarding.json<br>ExistingVmssOnboarding.json | Enables VM insights on existing virtual machine scale set. |
80
+
| NewVmssOnboarding | NewVmssOnboarding.json<br>NewVmssOnboarding.json | Creates a Virtual Machine Scale Set and enables it to be monitored with VM insights. |
81
+
| ExistingVmssOnboarding | ExistingVmssOnboarding.json<br>ExistingVmssOnboarding.json | Enables VM insights on existing Virtual Machine Scale Set. |
82
82
| ExistingArcVmOnboarding | ExistingArcVmOnboarding.json<br>ExistingArcVmOnboarding.json | Enables VM insights on existing Arc-enabled server. |
az deployment group create --resource-group <ResourceGroupName> --template-file <Template.json> --parameters <Parameters.json>
95
95
```
96
96
97
-
## To deploy a resource manager template
98
-
Each folder in the download has a template and a parameters file. Modify the parameters file with required details such as Virtual Machine Resource ID, Workspace resource ID, data collection rule resource ID, Location, and OS Type. Do not modify the template file unless you need to customize it for your particular scenario.
97
+
## To deploy a Resource Manager template
98
+
Each folder in the download has a template and a parameters file. Modify the parameters file with required details such as Virtual Machine Resource ID, Workspace resource ID, data collection rule resource ID, Location, and OS Type. Don't modify the template file unless you need to customize it for your particular scenario.
99
99
100
100
### Deploy with the Azure portal
101
101
See [Quickstart: Create and deploy ARM templates by using the Azure portal](../../azure-resource-manager/resource-manager-quickstart-create-templates-use-the-portal.md) for details on deploying a template from the Azure portal.
Copy file name to clipboardExpand all lines: articles/azure-monitor/vm/vminsights-health-overview.md
+7-9Lines changed: 7 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -18,7 +18,7 @@ VM insights guest health allows you to view the health of virtual machines based
18
18
See [Enable VM insights guest health (preview)](vminsights-health-enable.md) for details on enabling the guest health feature and onboarding virtual machines.
19
19
20
20
## Pricing
21
-
There is no direct cost for the guest health feature, but there is a cost for ingestion and storage of health state data in the Log Analytics workspace. All data is stored in the *HealthStateChangeEvent* table. See [Azure Monitor Logs pricing details](../logs/cost-logs.md) for details on pricing models and costs.
21
+
There's no direct cost for the guest health feature, but there's a cost for ingestion and storage of health state data in the Log Analytics workspace. All data is stored in the *HealthStateChangeEvent* table. See [Azure Monitor Logs pricing details](../logs/cost-logs.md) for details on pricing models and costs.
22
22
23
23
## View virtual machine health
24
24
The **Guest VM Health** column in the **Get Started** page gives you a quick view of the health of each virtual machine in a particular subscription or resource group. The current health of each virtual machine is displayed while icons for each group show the number of virtual machines currently in each state in that group.
@@ -27,7 +27,7 @@ The **Guest VM Health** column in the **Get Started** page gives you a quick vie
27
27
28
28
29
29
## Monitors
30
-
Click on a virtual machine's health status to view the detailed status for each of its monitors. Each monitor measures the health of a particular component. The overall health of the virtual machine is determined by the health of its individual monitors.
30
+
Select a virtual machine's health status to view the detailed status for each of its monitors. Each monitor measures the health of a particular component. The overall health of the virtual machine is determined by the health of its individual monitors.
@@ -45,9 +45,9 @@ The following table lists the aggregate and unit monitors currently available fo
45
45
| Available memory | Unit | Available megabytes on the VM. |
46
46
47
47
## Health states
48
-
Each monitor samples values on the agent every minute and compares sampled values to the criteria for each health state. If the criteria for particular state is true, then the monitor is set to that state. If none of the criteria are true, then the monitor is set to a healthy state. Data is sent from the agent to Azure Monitor every three minutes or immediately if there is a state change.
48
+
Each monitor samples values on the agent every minute and compares sampled values to the criteria for each health state. If the criteria for particular state are true, the monitor is set to that state. If none of the criteria are true, then the monitor is set to a healthy state. Data is sent from the agent to Azure Monitor every three minutes or immediately if there's a state change.
49
49
50
-
Each monitor has a lookback window and analyzes any samples collected within that time. For example, a monitor may have a lookback window of 240 seconds looking for the maximum value among at least 2 sampled values but no more than the last 3. While values are sampled at a regular rate, the number sampled in a particular window may vary slightly if there is any disruption in the agent operation.
50
+
Each monitor has a lookback window and analyzes any samples collected within that time. For example, a monitor may have a lookback window of 240 seconds looking for the maximum value among at least two sampled values but no more than the last 3. While values are sampled at a regular rate, the number sampled in a particular window may vary slightly if there's any disruption in the agent operation.
51
51
52
52
Monitors each have the potential health states in the following table and will be in one and only one at any given time. When a monitor is initialized, it starts in a healthy state.
53
53
@@ -74,19 +74,19 @@ There are two types of monitors as shown in the following table.
74
74
### Health rollup policy
75
75
The health state of a virtual machine is determined by the rollup of health from each of its unit and aggregate monitors. Each aggregate monitor uses a worst state health rollup policy where the state of the aggregate monitor matches the state of the child monitor with the worst health state.
76
76
77
-
In the following example, the **Free space** monitor is in a critical state which roles up to the aggregates for its instance and then to **File systems**. Even though **CPU utilization**in in a warning state, the virtual machine is set to critical since this is the worst state underneath it. If the free space were to return to a healthy state, then the virtual machine would change to a warning state since CPU utilization would then become the monitor with the worst state.
77
+
In the following example, the **Free space** monitor is in a critical state which roles up to the aggregates for its instance and then to **File systems**. Even though **CPU utilization**is in a warning state, the virtual machine is set to critical since this is the worst state underneath it. If the free space were to return to a healthy state, then the virtual machine would change to a warning state since CPU utilization would then become the monitor with the worst state.
Select a monitor to view its detail which includes the following tabs.
83
+
Select a monitor to view its details, including the following tabs.
84
84
85
85
**Overview** provides a description of the monitor, the last time it was evaluated, and values sampled to determine the current health state. The number of samples may vary based on the definition of the monitor and the volatility of the values.
**History** lists the history of state changes for the monitor. You can expand any of the state changes to view values evaluated to determine the health state. Click**View configuration applied** to view the configuration of the monitor at the time that the health state was changed.
89
+
**History** lists the history of state changes for the monitor. You can expand any of the state changes to view values evaluated to determine the health state. Select**View configuration applied** to view the configuration of the monitor at the time that the health state was changed.
90
90
91
91
92
92
@@ -98,8 +98,6 @@ View and modify the configuration of the monitor for the selected VM. See [Confi
0 commit comments