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/diagnostics-extension-overview.md
+32-35Lines changed: 32 additions & 35 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -18,25 +18,25 @@ Azure Diagnostics extension is an [agent in Azure Monitor](../agents/agents-over
18
18
19
19
Use Azure Diagnostics extension if you need to:
20
20
21
-
- Send data to Azure Storage for archiving or to analyze it with tools such as [Azure Storage Explorer](../../vs-azure-tools-storage-manage-with-storage-explorer.md).
22
-
- Send data to [Azure Monitor Metrics](../essentials/data-platform-metrics.md) to analyze it with [metrics explorer](../essentials/metrics-getting-started.md) and to take advantage of features such as near-real-time [metric alerts](../alerts/alerts-metric-overview.md) and [autoscale](../autoscale/autoscale-overview.md) (Windows only).
23
-
- Send data to third-party tools by using [Azure Event Hubs](./diagnostics-extension-stream-event-hubs.md).
24
-
- Collect [boot diagnostics](/troubleshoot/azure/virtual-machines/boot-diagnostics) to investigate VM boot issues.
21
+
* Send data to Azure Storage for archiving or to analyze it with tools such as [Azure Storage Explorer](../../vs-azure-tools-storage-manage-with-storage-explorer.md).
22
+
* Send data to [Azure Monitor Metrics](../essentials/data-platform-metrics.md) to analyze it with [metrics explorer](../essentials/metrics-getting-started.md) and to take advantage of features such as near-real-time [metric alerts](../alerts/alerts-metric-overview.md) and [autoscale](../autoscale/autoscale-overview.md) (Windows only).
23
+
* Send data to third-party tools by using [Azure Event Hubs](./diagnostics-extension-stream-event-hubs.md).
24
+
* Collect [boot diagnostics](/troubleshoot/azure/virtual-machines/boot-diagnostics) to investigate VM boot issues.
25
25
26
26
Limitations of Azure Diagnostics extension:
27
27
28
-
- It can only be used with Azure resources.
29
-
- It has limited ability to send data to Azure Monitor Logs.
28
+
* It can only be used with Azure resources.
29
+
* It has limited ability to send data to Azure Monitor Logs.
30
30
31
31
## Comparison to Log Analytics agent
32
32
33
33
The Log Analytics agent in Azure Monitor can also be used to collect monitoring data from the guest operating system of virtual machines. You can choose to use either or both depending on your requirements. For a comparison of the Azure Monitor agents, see [Overview of the Azure Monitor agents](../agents/agents-overview.md).
34
34
35
35
The key differences to consider are:
36
36
37
-
- Azure Diagnostics Extension can be used only with Azure virtual machines. The Log Analytics agent can be used with virtual machines in Azure, other clouds, and on-premises.
38
-
- Azure Diagnostics extension sends data to Azure Storage, [Azure Monitor Metrics](../essentials/data-platform-metrics.md) (Windows only) and Azure Event Hubs. The Log Analytics agent collects data to [Azure Monitor Logs](../logs/data-platform-logs.md).
39
-
- The Log Analytics agent is required for retired [solutions](/previous-versions/azure/azure-monitor/insights/solutions), [VM insights](../vm/vminsights-overview.md), and other services such as [Microsoft Defender for Cloud](../../security-center/index.yml).
37
+
* Azure Diagnostics Extension can be used only with Azure virtual machines. The Log Analytics agent can be used with virtual machines in Azure, other clouds, and on-premises.
38
+
* Azure Diagnostics extension sends data to Azure Storage, [Azure Monitor Metrics](../essentials/data-platform-metrics.md) (Windows only) and Azure Event Hubs. The Log Analytics agent collects data to [Azure Monitor Logs](../logs/data-platform-logs.md).
39
+
* The Log Analytics agent is required for retired [solutions](/previous-versions/azure/azure-monitor/insights/solutions), [VM insights](../vm/vminsights-overview.md), and other services such as [Microsoft Defender for Cloud](../../security-center/index.yml).
40
40
41
41
## Costs
42
42
@@ -116,24 +116,23 @@ The following tables list the operating systems that are supported by WAD and LA
| Windows 10 Enterprise<br>(including multi-session) and Pro<br>(Server scenarios only<sup>1</sup>) |X |
130
+
| Windows 10 Enterprise<br>(including multi-session) and Pro<br>(Server scenarios only<sup>1</sup>) |✅|
131
131
| Windows 8 Enterprise and Pro<br>(Server scenarios only<sup>1</sup>) ||
132
132
| Windows 7 SP1<br>(Server scenarios only<sup>1</sup>) ||
133
133
| Azure Stack HCI ||
134
134
135
135
<sup>1</sup> Running the OS on server hardware, for example, machines that are always connected, always turned on, and not running other workloads (PC, office, browser)<br>
136
-
<sup>2</sup> Using the Azure Monitor agent [client installer (preview)](./azure-monitor-agent-windows-client.md)
137
136
138
137
### Linux
139
138
@@ -143,40 +142,38 @@ The following tables list the operating systems that are supported by WAD and LA
143
142
| Amazon Linux 2017.09 ||
144
143
| Amazon Linux 2 ||
145
144
| CentOS Linux 8 ||
146
-
| CentOS Linux 7 |X |
145
+
| CentOS Linux 7 |✅|
147
146
| CentOS Linux 6 ||
148
-
| CentOS Linux 6.5+ |X |
147
+
| CentOS Linux 6.5+ |✅|
149
148
| Debian 11 <sup>1</sup> ||
150
149
| Debian 10 <sup>1</sup> ||
151
-
| Debian 9 |X |
150
+
| Debian 9 |✅|
152
151
| Debian 8 ||
153
-
| Debian 7 |X |
154
-
| OpenSUSE 13.1+ |X |
152
+
| Debian 7 |✅|
153
+
| OpenSUSE 13.1+ |✅|
155
154
| Oracle Linux 8 ||
156
-
| Oracle Linux 7 |X |
155
+
| Oracle Linux 7 |✅|
157
156
| Oracle Linux 6 ||
158
-
| Oracle Linux 6.4+ |X |
157
+
| Oracle Linux 6.4+ |✅|
159
158
| Red Hat Enterprise Linux Server 8.5, 8.6 ||
160
159
| Red Hat Enterprise Linux Server 8, 8.1, 8.2, 8.3, 8.4 ||
161
-
| Red Hat Enterprise Linux Server 7 |X |
160
+
| Red Hat Enterprise Linux Server 7 |✅|
162
161
| Red Hat Enterprise Linux Server 6 ||
163
-
| Red Hat Enterprise Linux Server 6.7+ |X |
162
+
| Red Hat Enterprise Linux Server 6.7+ |✅|
164
163
| Rocky Linux ||
165
164
| SUSE Linux Enterprise Server 15.2 ||
166
165
| SUSE Linux Enterprise Server 15.1 ||
167
166
| SUSE Linux Enterprise Server 15 SP1 ||
168
167
| SUSE Linux Enterprise Server 15 ||
169
-
| SUSE Linux Enterprise Server 12 SP5 |X |
170
-
| SUSE Linux Enterprise Server 12 |X |
168
+
| SUSE Linux Enterprise Server 12 SP5 |✅|
169
+
| SUSE Linux Enterprise Server 12 |✅|
171
170
| Ubuntu 22.04 LTS ||
172
-
| Ubuntu 20.04 LTS |X <sup>4</sup>|
173
-
| Ubuntu 18.04 LTS |X |
174
-
| Ubuntu 16.04 LTS |X |
175
-
| Ubuntu 14.04 LTS |X |
171
+
| Ubuntu 20.04 LTS |✅ |
172
+
| Ubuntu 18.04 LTS |✅|
173
+
| Ubuntu 16.04 LTS |✅|
174
+
| Ubuntu 14.04 LTS |✅|
176
175
177
176
<sup>1</sup> Requires Python (2 or 3) to be installed on the machine.<br>
178
-
<sup>2</sup> Known issue collecting Syslog events in versions prior to 1.9.0.<br>
179
-
<sup>3</sup> Not all kernel versions are supported. Check the supported kernel versions in the following table.
0 commit comments