Skip to content

Commit 86552a2

Browse files
Merge pull request #268409 from JeffreyWolford/patch-20
Update data-collection-syslog.md
2 parents 5776e1a + 1caae69 commit 86552a2

File tree

1 file changed

+19
-14
lines changed

1 file changed

+19
-14
lines changed

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

Lines changed: 19 additions & 14 deletions
Original file line numberDiff line numberDiff line change
@@ -20,24 +20,29 @@ When the Azure Monitor agent for Linux is installed, it configures the local Sys
2020
:::image type="content" source="media/azure-monitor-agent/linux-agent-syslog-communication.png" lightbox="media/azure-monitor-agent/linux-agent-syslog-communication.png" alt-text="Diagram that shows Syslog daemon and Azure Monitor Agent communication.":::
2121

2222
The following facilities are supported with the Syslog collector:
23-
* alert
24-
* audit
25-
* auth
26-
* authpriv
27-
* clock (formerly mark)
28-
* cron
23+
* None
24+
* Kern
25+
* user
26+
* mail
2927
* daemon
30-
* ftp
31-
* kern
32-
* local0-local7
28+
* auth
29+
* syslog
3330
* lpr
34-
* mail
3531
* news
36-
* nopri
37-
* ntp
38-
* syslog
39-
* user
4032
* uucp
33+
* ftp
34+
* ntp
35+
* audit
36+
* alert
37+
* mark
38+
* local0
39+
* local1
40+
* local2
41+
* local3
42+
* local4
43+
* local5
44+
* local6
45+
* local7
4146

4247
For some device types that don't allow local installation of Azure Monitor Agent, the agent can be installed instead on a dedicated Linux-based log forwarder. The originating device must be configured to send Syslog events to the Syslog daemon on this forwarder instead of the local daemon. For more information, see the [Sentinel tutorial](../../sentinel/forward-syslog-monitor-agent.md).
4348

0 commit comments

Comments
 (0)