

Syslog records have a type of Syslog and have the properties in the following table.


# Warnings (except iptables) in one file:ĭestination warn Īfter completing the changes, the Syslog and the Log Analytics agent service needs to be restarted to ensure the configuration changes take effect. This collects syslog messages sent from the local agent for all facilities and all severities. For example, to limit the user facility to messages with a severity of error or higher you would modify that line of the configuration file to the following: user.error configuration file for syslog-ng is location at /etc/syslog-ng/nf. You can limit the severities that are collected for a particular facility by modifying that facility's entry. kern.warning can remove a facility by removing its section of the configuration file. This collects syslog messages sent from the local agent for all facilities with a level of warning or higher. The configuration file for rsyslog is located at /etc/rsyslog.d/nf. If you edit the syslog configuration, you must restart the syslog daemon for the changes to take effect. The configuration file is different depending on the Syslog daemon that the client has installed. You can modify this file to change the configuration. When the Log Analytics agent is installed on a Linux client, it installs a default syslog configuration file that defines the facility and severity of the messages that are collected. If you want to configure Syslog manually on each Linux agent, then uncheck the box Apply below configuration to my machines. You cannot provide any additional criteria to filter messages.īy default, all configuration changes are automatically pushed to all agents. Check the severities for the particular facility that you want to collect. For each facility, only messages with the selected severities will be collected. You can add a new facility by clicking Add facility. This configuration is delivered to the configuration file on each Linux agent. Configure Syslog in the Azure portalĬonfigure Syslog from the Agent configuration menu for the Log Analytics workspace. You can configure Syslog through the Azure portal or by managing configuration files on your Linux agents. The Log Analytics agent for Linux will only collect events with the facilities and severities that are specified in its configuration. The following facilities are supported with the Syslog collector:įor any other facility, configure a Custom Logs data source in Azure Monitor. To collect syslog data from this version of these distributions, the rsyslog daemon should be installed and configured to replace sysklog. 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. Azure Monitor supports collection of messages sent by rsyslog or syslog-ng, where rsyslog is the default daemon.
