This object contains global parameters relating to the syslog implementations that is active in the Device. Based on {{bibref|YANGSYSLOG|A YANG Data Model for Syslog Configuration}}. Enables or disables the Syslog service. Indicates the syslog service operational state. Indicates that the Syslog service is disabled. Indicates that the Syslog service is enabled. Indicates that the Syslog service has encountered an error. {{numentries}} {{numentries}} {{numentries}} {{numentries}} This table defines the processing used to select log messages by comparing syslog message with the provided rules. A rule can consist either of {{param|FacilityLevel}} - {{param|Severity}} and or {{param|PatternMatch}}. Only the log messages with following Facility levels must be logged. Kernel messages (0). User-level messages (1). Mail system messages (2). System daemons messages (3). Security/authorization messages (4). Messages generated internally by syslogd (5). Line printer subsystem messages (6). Network news subsystem (7). UUCP subsystem messages (8). Clock daemon messages (9). Security/authorization messages (10). FTP daemon messages (11). NTP subsystem messages (12). Log audit messages (13). Log alert messages (14). Second clock daemon messages (15). Local use 0 messages (16). Local use 1 messages (17). local use 2 messages (18). local use 3 messages (19). local use 4 messages (20). local use 5 messages (21). local use 6 messages (22). local use 7 messages (23). All facilities are selected. Specifies the Severity level filter rules. Defines the processing used to select log messages by comparing syslog message severity using the following processing rules: - if 'none', do not match. - if 'all', match. - else compare message severity with the specified severity according to the default compare rule (all messages of the specified severity and greater match). This must be used inconjuction with {{param|SeverityCompare}} and {{param|SeverityCompareAction}}. Indicates that the system is unusable. Indicating that an action must be taken immediately. Indicates a critical condition. Indicates a errors condition. Indicates a warning condition. Indicates a normal but important message. Indicates an informational message. Indicates a debug-level message. All severities are selected. No filtering will be applied. Describes the comparison method that must be applied when a syslog message is received. Not applicable when severity {{enum|All|Severity}} and {{enum|None|Severity}} is configured. Specifies that the severity comparison operation will be equals. Specifies that the severity comparison operation will be equals or higher." Specifies the process of handling a syslog message based on specified conditions. It defines the action that will be taken when the criteria of both {{param|Severity}} and {{param|SeverityCompare}} are met, determining the response to the syslog message. When the selected comparison is true the syslog message will be logged. When the selected comparison is true the syslog message will not be logged. When the select comparison is true the syslog message will not be logged and no further processing will occur." Regular expression pattern designed to match a syslog message that must be logged. The format is implementation specific. This table describes where and how the syslog service receives log messages. This option enables the collection of kernel log messages that are specific to the Device. This option enables the collection of the system log messages that are specific to the Device. Specifies the default Severity. When an incoming message lacks a valid syslog header, this parameter can be used to configure the required Severity level. Indicates that the system is unusable. Indicating that an action must be taken immediately. Indicates a critical condition. Indicates a errors condition. Indicates a warning condition. Indicates a normal but important message. Indicates an informational message. Indicates a debug-level message. All severities are selected. No filtering will be applied. Specifies the default Facility Level. When an incoming message lacks a valid syslog header, this parameter can be used to configure the required Facility level. Kernel messages (0). User-level messages (1). Mail system messages (2). System daemons messages (3). Security/authorization messages (4). Messages generated internally by syslogd (5). Line printer subsystem messages (6). Network news subsystem (7). UUCP subsystem messages (8). Clock daemon messages (9). Security/authorization messages (10). FTP daemon messages (11). NTP subsystem messages (12). Log audit messages (13). Log alert messages (14). Second clock daemon messages (15). Local use 0 messages (16). Local use 1 messages (17). local use 2 messages (18). local use 3 messages (19). local use 4 messages (20). local use 5 messages (21). local use 6 messages (22). local use 7 messages (23). All facilities are selected. This object describes the configuration parameters for receiving syslog information on a network socket. Enables or disables the functionality to receive syslog information on a network socket. The IP or Logical Interface on which the syslog information will be received. When {{empty}} is specified the syslog service will listen to all available network interfaces. Example: * ''Device.IP.Interface.1'' * ''Device.Logical.Interface.1'' {{template|INTERFACE-ROUTING}} Specifies the port number on which the syslog information will be received. The protocol to be used for receiving syslog information. {{bibref|RFC6587|Transmission of Syslog Messages over TCP}}. {{bibref|RFC5426|Transmission of Syslog Messages over UDP}}. {{bibref|RFC5425|Transport Layer Security (TLS) Transport Mapping for Syslog}}. Ensures authentic and secure connections by validating entity credentials such as certificates or tokens. Only applicable when {{param|Protocol}} is set to {{enum|TLS|Protocol}}. In order to validate a certificate, the entire certificate chain, including the CA certificate, must be valid. If any certificate in the chain is found to be invalid, the syslog service must reject the connection. This table the describes the templates that can be referenced by objects that can use the template syntax. With templates, you have the flexibility to establish uniform message formats or even define standard filenames for different objects. Describes the template syntax used for transforming the syslog message. The format is implementation specific and can consist of strings, macros, and template functions. Enabling this option will cause the following characters to be escaped ', " and \. in the syslog message. This object describes the log action parameters for syslog. Mandatory parameter. Specifies one or multiple sources from where the log messages originate. The Filter associated with the {{object}} entry. When referencing multiple Filter rules, it is mandatory to execute them in the order listed within the parameter. Example: FilterRef=.Syslog.Filter.3,.Syslog.Filter.1 First filter rule 3 must be executed and then filter rule 1. When no Filter is specified the log message will not be filtered. The Template associated with the {{object}} entry. When no Template is specified the log message will not be altered by the template system. This feature represents the ability to log messages in structured-data format. Reference {{bibref|RFC5424|The Syslog Protocol}}. This object describes the configuration parameters for file logging. If file-archive limits are not supplied, it is assumed that the local implementation defined limits will be used. Enables or disables the LogFile functionality. The reference to {{object|###.DeviceInfo.VendorLogFile}} is automatically constructed and the {{object|###.DeviceInfo.VendorLogFile}} is populated with the information based on {{param|FilePath}}. E.g. When {{param|FilePath}} = ''file:///var/log/messages''. The following entry is automatically added to {{object|###.DeviceInfo.VendorLogFile}}: ''file:///var/log/messages''. Destination path and filename of where to create and keep the logfiles. Which MUST use the uri scheme file {{bibref|RFC8089|The file URI Scheme}}. This object describes the configuration parameters for forwarding syslog messages to remote relays or collectors. Enables or disables the LogRemote functionality. Status of the remote log destination. Indicates that the Syslog remote destination is disabled. Indicates that the Syslog remote destination is enabled. Indicate that the Syslog remote destination is unreachable. Indicates that the Syslog remote destination is misconfigured or has encountered an error. Host name or IP address of the remote server. Protocol to be used to deliver the syslog messages to the remote server. Note: This parameter was promoted to readWrite in the Device:2.18 version. {{bibref|RFC6587|Transmission of Syslog Messages over TCP}}. {{bibref|RFC5426|Transmission of Syslog Messages over UDP}}. {{bibref|RFC5425|Transport Layer Security (TLS) Transport Mapping for Syslog}}. Port number of the remote server. Ensures authentic and secure connections by validating entity credentials such as certificates or tokens. Only applicable when {{param|Protocol}} is set to {{enum|TLS|Protocol}}. In order to validate a certificate, the entire certificate chain, including the CA certificate, must be valid. If any certificate in the chain is found to be invalid, the syslog service must reject the connection. Syslog event Contains the complete syslog message.