Managing the Syslog-Based Error Log Publisher
The PingDirectory server supports a Syslog-Based Error Log Publisher using the same mechanism as the Syslog-Based Access Log Publisher.
Configure the error logger using the dsconfig
tool.
Syslog error mapping
The PingDirectory server automatically maps error log severities to the syslog severities. The following mappings are used.
Error Log Severities | Syslog Severity |
---|---|
FATAL_ERROR,0 |
Syslog Emergency |
SEVERE_ERROR,1 |
Syslog Alert |
SEVERE_WARNING,2 |
Syslog Critical |
MILD_ERROR,3 |
Syslog Error |
MILD_WARNING,4 |
Syslog Warn |
NOTICE,5 |
Syslog Notice |
INFORMATION,6 |
Syslog Info |
DEBUG,7 |
Syslog Debug |
Configuring a Syslog-Based Error Log Publisher
About this task
Configure a Syslog-based Error Log Publisher using the dsconfig
tool. You should use syslog locally on localhost
and use syslog-ng
to send the data packets over the UDP protocol.
Because syslog implementations differ by vendor, review your particular vendor’s syslog configuration.
Steps
-
Use
dsconfig
to create a log publisher of typesyslog-based-error
.Example:
In this example, set the syslog facility to 4 for security/authorization messages.
$ bin/dsconfig create-log-publisher --publisher-name "syslog-error" \ --type syslog-based-error --set syslog-facility:4 --set enabled:true