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/platform/log-analytics-agent.md
+18-2Lines changed: 18 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -11,7 +11,7 @@ ms.service: log-analytics
11
11
ms.workload: na
12
12
ms.tgt_pltfrm: na
13
13
ms.topic: conceptual
14
-
ms.date: 04/22/2019
14
+
ms.date: 06/06/2019
15
15
ms.author: magoedte
16
16
---
17
17
@@ -54,7 +54,8 @@ Starting with versions released after August 2018, we are making the following c
54
54
* New versions of AMI are not supported.
55
55
* Only versions that run SSL 1.x by default are supported.
56
56
57
-
If you are using a distro or version that is not currently supported and doesn't align to our support model, we recommend that you fork this repo, acknowledging that Microsoft support will not provide assistance with forked agent versions.
57
+
>[!NOTE]
58
+
>If you are using a distro or version that is not currently supported and doesn't align to our support model, we recommend that you fork this repo, acknowledging that Microsoft support will not provide assistance with forked agent versions.
58
59
59
60
* Amazon Linux 2017.09 (x64)
60
61
* CentOS Linux 6 (x86/x64) and 7 (x64)
@@ -68,6 +69,21 @@ If you are using a distro or version that is not currently supported and doesn't
68
69
>OpenSSL 1.1.0 is only supported on x86_x64 platforms (64-bit) and OpenSSL earlier than 1.x is not supported on any platform.
69
70
>
70
71
72
+
### Agent prerequisites
73
+
74
+
The following table highlights the packages required for supported Linux distros that the agent will be installed on.
75
+
76
+
|Required package |Description |Minimum version |
77
+
|-----------------|------------|----------------|
78
+
|Glibc | GNU C Library | 2.5-12
79
+
|Openssl | OpenSSL Libraries | 1.0.x or 1.1.x |
80
+
|Curl | cURL web client | 7.15.5 |
81
+
|Python-ctypes ||
82
+
|PAM | Pluggable Authentication Modules ||
83
+
84
+
>[!NOTE]
85
+
>Either rsyslog or syslog-ng are required to collect syslog messages. The default syslog daemon on version 5 of Red Hat Enterprise Linux, CentOS, and Oracle Linux version (sysklog) is not supported for syslog event collection. To collect syslog data from this version of these distributions, the rsyslog daemon should be installed and configured to replace sysklog.
86
+
71
87
## TLS 1.2 protocol
72
88
To insure the security of data in transit to Azure Monitor logs, we strongly encourage you to configure the agent to use at least Transport Layer Security (TLS) 1.2. Older versions of TLS/Secure Sockets Layer (SSL) have been found to be vulnerable and while they still currently work to allow backwards compatibility, they are **not recommended**. For additional information, review [Sending data securely using TLS 1.2](../../azure-monitor/platform/data-security.md#sending-data-securely-using-tls-12).
Copy file name to clipboardExpand all lines: articles/azure-monitor/platform/vmext-troubleshoot.md
+6-11Lines changed: 6 additions & 11 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -11,7 +11,7 @@ ms.service: log-analytics
11
11
ms.topic: conceptual
12
12
ms.tgt_pltfrm: na
13
13
ms.workload: infrastructure-services
14
-
ms.date: 01/08/2018
14
+
ms.date: 06/06/2019
15
15
ms.author: magoedte
16
16
---
17
17
@@ -40,16 +40,11 @@ If the *Microsoft Monitoring Agent* VM extension is not installing or reporting,
40
40
* You can also review the VM agent log file `C:\WindowsAzure\logs\WaAppAgent.log`
41
41
* If the log does not exist, the VM agent is not installed.
42
42
*[Install the Azure VM Agent](../../azure-monitor/learn/quick-collect-azurevm.md#enable-the-log-analytics-vm-extension)
43
-
2. Confirm the Microsoft Monitoring Agent extension heartbeat task is running using the following steps:
44
-
* Log in to the virtual machine
45
-
* Open task scheduler and find the `update_azureoperationalinsight_agent_heartbeat` task
46
-
* Confirm the task is enabled and is running every one minute
47
-
* Check the heartbeat logfile in `C:\WindowsAzure\Logs\Plugins\Microsoft.EnterpriseCloud.Monitoring.MicrosoftMonitoringAgent\heartbeat.log`
48
-
3. Review the Microsoft Monitoring Agent VM extension log files in `C:\Packages\Plugins\Microsoft.EnterpriseCloud.Monitoring.MicrosoftMonitoringAgent`
49
-
4. Ensure the virtual machine can run PowerShell scripts
50
-
5. Ensure permissions on C:\Windows\temp haven’t been changed
51
-
6. View the status of the Microsoft Monitoring Agent by typing the following in an elevated PowerShell window on the virtual machine `(New-Object -ComObject 'AgentConfigManager.MgmtSvcCfg').GetCloudWorkspaces() | Format-List`
52
-
7. Review the Microsoft Monitoring Agent setup log files in `C:\Windows\System32\config\systemprofile\AppData\Local\SCOM\Logs`
43
+
2. Review the Microsoft Monitoring Agent VM extension log files in `C:\Packages\Plugins\Microsoft.EnterpriseCloud.Monitoring.MicrosoftMonitoringAgent`
44
+
3. Ensure the virtual machine can run PowerShell scripts
45
+
4. Ensure permissions on C:\Windows\temp haven’t been changed
46
+
5. View the status of the Microsoft Monitoring Agent by typing the following in an elevated PowerShell window on the virtual machine `(New-Object -ComObject 'AgentConfigManager.MgmtSvcCfg').GetCloudWorkspaces() | Format-List`
47
+
6. Review the Microsoft Monitoring Agent setup log files in `C:\Windows\System32\config\systemprofile\AppData\Local\SCOM\Logs`
53
48
54
49
For more information, see [troubleshooting Windows extensions](../../virtual-machines/extensions/oms-windows.md).
Copy file name to clipboardExpand all lines: articles/virtual-machines/extensions/oms-linux.md
+17-1Lines changed: 17 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -14,7 +14,7 @@ ms.devlang: na
14
14
ms.topic: article
15
15
ms.tgt_pltfrm: vm-linux
16
16
ms.workload: infrastructure-services
17
-
ms.date: 03/12/2019
17
+
ms.date: 06/06/2019
18
18
ms.author: roiyz
19
19
20
20
---
@@ -49,11 +49,27 @@ The Log Analytics Agent extension can be run against these Linux distributions.
49
49
>OpenSSL lower than version 1.x is not supported on any platform, and version 1.10 is only supported on x86_64 platforms (64-bit).
50
50
>
51
51
52
+
### Agent prerequisites
53
+
54
+
The following table highlights the packages required for supported Linux distros that the agent will be installed on.
55
+
56
+
|Required package |Description |Minimum version |
57
+
|-----------------|------------|----------------|
58
+
|Glibc | GNU C Library | 2.5-12
59
+
|Openssl | OpenSSL Libraries | 1.0.x or 1.1.x |
60
+
|Curl | cURL web client | 7.15.5 |
61
+
|Python-ctypes ||
62
+
|PAM | Pluggable Authentication Modules ||
63
+
64
+
>[!NOTE]
65
+
>Either rsyslog or syslog-ng are required to collect syslog messages. The default syslog daemon on version 5 of Red Hat Enterprise Linux, CentOS, and Oracle Linux version (sysklog) is not supported for syslog event collection. To collect syslog data from this version of these distributions, the rsyslog daemon should be installed and configured to replace sysklog.
66
+
52
67
### Agent and VM Extension version
53
68
The following table provides a mapping of the version of the Azure Monitor VM extension and Log Analytics agent bundle for each release. A link to the release notes for the Log Analytics agent bundle version is included. Release notes include details on bug fixes and new features available for a given agent release.
54
69
55
70
| Azure Monitor Linux VM extension version | Log Analytics Agent bundle version |
0 commit comments