Skip to content

Commit fdbc6ee

Browse files
authored
Update data-collection-syslog.md
1 parent 3bff30d commit fdbc6ee

File tree

1 file changed

+17
-0
lines changed

1 file changed

+17
-0
lines changed

articles/azure-monitor/agents/data-collection-syslog.md

Lines changed: 17 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,3 +1,4 @@
1+
12
---
23
title: Collect Syslog events with Azure Monitor Agent
34
description: Configure collection of Syslog events by using a data collection rule on virtual machines with Azure Monitor Agent.
@@ -199,6 +200,22 @@ log {
199200
flags(flow-control);
200201
};
201202
```
203+
>[!Note]
204+
>The following configuration is used when you use SELinux and we decide to use Unix sockets.
205+
```
206+
$ cat /etc/syslog-ng/conf.d/azuremonitoragent.conf
207+
# Azure MDSD configuration: syslog forwarding config for mdsd agent options {};
208+
# during install time, we detect if s_src exist, if it does then we
209+
# replace it by appropriate source name like in redhat 's_sys'
210+
# Forwrding using unix domain socket
211+
destination d_azure_mdsd {
212+
unix-dgram("/run/azuremonitoragent/default_syslog.socket"
213+
flags(no_multi_line)
214+
);
215+
};
216+
log { source(s_src); # will be automatically parsed from /etc/syslog-ng/syslog-ng.conf
217+
destination(d_azure_mdsd); };
218+
```
202219

203220
>[!Note]
204221
> Azure Monitor supports collection of messages sent by rsyslog or syslog-ng, where rsyslog is the default daemon. The default Syslog daemon on version 5 of Red Hat Enterprise Linux, CentOS, and Oracle Linux version (sysklog) isn't 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.

0 commit comments

Comments
 (0)