| Home Prev |  InCenter 2.2.5 On-Premises Administration Guide
|
Next |
|---|
The log messages generated by InCenter itself can be sent to one or more external Syslog servers. InCenter Syslog messaging complies with RFC 5424. Note that the log messages sent to InCenter cannot be forwarded to an external Syslog server.
Configuring Syslog Servers
Sending messages to a Syslog server is set up with the CLI command: add SyslogReceiver.Suppose that a Syslog server has the IPv4 address 192.0.2.10. The simplest CLI command to set up this server for logging InCenter events would be:
admin@InCenter:/> add SyslogReceiver Name=my_logger
IP=192.0.2.10Any number of SyslogReceiver objects can exist at the same time.
The optional SyslogReceiver object properties are the following:
Port - The port number for connection. The default is 514.
Severity - The severities to be sent. The possible values are: Informational, Notice, Warning, Error, Critical, Alert, Emergency and Debug.
The default value is Informational, Notice, Warning, Error, Critical, Alert, Emergency.
Category - The categories of messages sent. The default is All but this could be any combination of: Config, DB, License, REST, SSH and System.
LogType - This can be Audit and/or System. The default is both.
Facility - This can be local0 through local7. The default is local0.
InCenter will scan all configured SyslogReceiver objects and send a log message to the receiver if the message matches the filtering criteria of the object.
