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/agents/azure-monitor-agent-manage.md
+32-9Lines changed: 32 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -28,13 +28,14 @@ WE strongly recommended to update to generally available versions listed as foll
28
28
|:---|:---|:---|:---|:---|
29
29
| June 2021 | General availability announced. <ul><li>All features except metrics destination now generally available</li><li>Production quality, security and compliance</li><li>Availability in all public regions</li><li>Performance and scale improvements for higher EPS</li></ul> [Learn more](https://azure.microsoft.com/updates/azure-monitor-agent-and-data-collection-rules-now-generally-available/)| 1.0.12.0 | 1.9.1.0 |
30
30
| July 2021 | <ul><li>Support for direct proxies</li><li>Support for Log Analytics gateway</li></ul> [Learn more](https://azure.microsoft.com/updates/general-availability-azure-monitor-agent-and-data-collection-rules-now-support-direct-proxies-and-log-analytics-gateway/)| 1.1.1.0 | 1.10.5.0 |
31
-
| August 2021 | Fixed issue allowing Azure Monitor Metrics as the only destination | 1.1.2.0 | 1.10.9.0<sup>1</sup> |
32
-
| September 2021 | <ul><li>Fixed issue causing data loss on restarting the agent</li><li>Addressed regression introduced in 1.1.3.1<sup>2</sup> for Arc Windows servers</li></ul> | 1.1.3.2 | 1.12.2.0 <sup>2</sup> |
33
-
| December 2021 | Fixed issues impacting Linux Arc-enabled servers | N/A | 1.14.7.0<sup>3</sup> |
31
+
| August 2021 | Fixed issue allowing Azure Monitor Metrics as the only destination | 1.1.2.0 | 1.10.9.0<sup>Hotfix</sup> |
32
+
| September 2021 | <ul><li>Fixed issue causing data loss on restarting the agent</li><li>Fixed issue for Arc Windows servers</li></ul> | 1.1.3.2<sup>Hotfix</sup> | 1.12.2.0 <sup>1</sup> |
33
+
| December 2021 | <ul><li>Fixed issues impacting Linux Arc-enabled servers</li><li>'Heartbeat' table > 'Category' column reports "Azure Monitor Agent" in Log Analytics for Windows</li></ul> | 1.1.4 | 1.14.7.0<sup>2</sup> |
34
+
| January 2021 | <ul><li>Syslog RFC compliance for Linux</li><li>Fixed issue for Linux perf counters not flowing on restart</li><ul> | Not available yet | 1.15.2<sup>Hotfix</sup> |
34
35
35
-
<sup>1</sup> Do not use AMA Linux version 1.10.7.0
36
-
<sup>2</sup> Known regression where it's not working on Arc-enabled servers
37
-
<sup>3</sup> Bug identified wherein Linux performance counters data stops flowing on restarting/rebooting the machine(s). Fix underway and will be available in next monthly version update.
36
+
<sup>Hotfix</sup> Do not use AMA Linux versions v1.10.7, v1.15.1 and AMA Windows v1.1.3.1. Please use hotfixed versions listed above.
37
+
<sup>1</sup> Known issue: No data collected from Linux Arc-enabled servers
38
+
<sup>2</sup> Known issue: Linux performance counters data stops flowing on restarting/rebooting the machine(s)
38
39
39
40
40
41
## Prerequisites
@@ -59,7 +60,7 @@ To uninstall the Azure Monitor agent using the Azure portal, navigate to your vi
59
60
60
61
### Update
61
62
To perform a **one time update** of the agent, you must first uninstall the existing agent version and then install the new version as described above.
62
-
63
+
The **recommendation** is to enable automatic update of the agent by enabling the [Automatic Extension Upgrade](../../virtual-machines/automatic-extension-upgrade.md) feature. Navigate to your virtual machine or scale set, select the **Extensions** tab and click on **AzureMonitorWindowsAgent** or **AzureMonitorLinuxAgent**. In the dialog that pops up, click **Enable automatic upgrade**.
To perform a **one time update** of the agent, you must first uninstall the existing agent version and then install the new version as described above.
115
+
To perform a **one time update** of the agent, you must first uninstall the existing agent version and then install the new version as described above.
116
+
The **recommendation** is to enable automatic update of the agent by enabling the [Automatic Extension Upgrade](../../virtual-machines/automatic-extension-upgrade.md) feature, using the following PowerShell commands.
Use the following PowerShell commands to install the Azure Monitor agent on Azure Arc-enabled servers.
@@ -192,7 +204,18 @@ az vm extension delete --resource-group <resource-group-name> --vm-name <virtual
192
204
---
193
205
194
206
### Update on Azure virtual machines
195
-
To perform a **one time update** of the agent, you must first uninstall the existing agent version and then install the new version as described above.
207
+
To perform a **one time update** of the agent, you must first uninstall the existing agent version and then install the new version as described above.
208
+
The **recommendation** is to enable automatic update of the agent by enabling the [Automatic Extension Upgrade](../../virtual-machines/automatic-extension-upgrade.md) feature, using the following CLI commands.
209
+
# [Windows](#tab/CLIWindows)
210
+
```azurecli
211
+
az vm extension set -name AzureMonitorWindowsAgent --publisher Microsoft.Azure.Monitor --vm-name <virtual-machine-name> --resource-group <resource-group-name> --enable-auto-upgrade true
212
+
```
213
+
# [Linux](#tab/CLILinux)
214
+
```azurecli
215
+
az vm extension set -name AzureMonitorLinuxAgent --publisher Microsoft.Azure.Monitor --vm-name <virtual-machine-name> --resource-group <resource-group-name> --enable-auto-upgrade true
216
+
```
217
+
---
218
+
196
219
197
220
### Install on Azure Arc-enabled servers
198
221
Use the following CLI commands to install the Azure Monitor agent onAzure Azure Arc-enabled servers.
Copy file name to clipboardExpand all lines: articles/azure-monitor/agents/azure-monitor-agent-overview.md
+6-4Lines changed: 6 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -108,11 +108,13 @@ The Azure Monitor agent sends data to Azure Monitor Metrics (preview) or a Log A
108
108
109
109
| Data source | Destinations | Description |
110
110
|:---|:---|:---|
111
-
| Performance | Azure Monitor Metrics (preview)<sup>1</sup><br>Log Analytics workspace | Numerical values measuring performance of different aspects of operating system and workloads |
112
-
| Windows event logs | Log Analytics workspace | Information sent to the Windows event logging system |
113
-
| Syslog | Log Analytics workspace | Information sent to the Linux event logging system |
111
+
| Performance | Azure Monitor Metrics (preview)<sup>1</sup> - Insights.virtualmachine namespace<br>Log Analytics workspace - [Perf](../reference/tables/perf.md) table | Numerical values measuring performance of different aspects of operating system and workloads |
112
+
| Windows event logs | Log Analytics workspace - [Event](../reference/tables/Event.md) table | Information sent to the Windows event logging system |
113
+
| Syslog | Log Analytics workspace - [Syslog](../reference/tables/syslog.md)<sup>2</sup> table | Information sent to the Linux event logging system |
114
+
115
+
<sup>1</sup> [Click here](../essentials/metrics-custom-overview.md#quotas-and-limits) to review other limitations of using Azure Monitor Metrics. On Linux, using Azure Monitor Metrics as the only destination is supported in v1.10.9.0 or higher.
116
+
<sup>2</sup> Azure Monitor Linux Agent v1.15.2 or higher supports syslog RFC formats including Cisco Meraki, Cisco ASA, Cisco FTD, Sophos XG, Juniper Networks, Corelight Zeek, CipherTrust, NXLog, McAfee and CEF (Common Event Format).
114
117
115
-
<sup>1</sup> [Click here](../essentials/metrics-custom-overview.md#quotas-and-limits) to review other limitations of using Azure Monitor Metrics. On Linux, using Azure Monitor Metrics as the only destination is supported in v.1.10.9.0 or higher.
116
118
117
119
## Security
118
120
The Azure Monitor agent doesn't require any keys but instead requires a [system-assigned managed identity](../../active-directory/managed-identities-azure-resources/qs-configure-portal-windows-vm.md#system-assigned-managed-identity). You must have a system-assigned managed identity enabled on each virtual machine before you deploy the agent.
0 commit comments