Logging to Syslog

Table of contents
  1. 1. Configuration
    1. 1.1. Enabled
    2. 1.2. Host
    3. 1.3. Port
    4. 1.4. Facility

Password Server can redirect log events to a Syslog server.

The Syslog protocol is a standard format for logging Event messages and is effective for consolidating logs from multiple different systems. It originates from and became a standard in Unix-based systems. For more details see: https://en.wikipedia.org/wiki/Syslog

It is useful in the administration of these aspects of log messages:

  • Managing system alerts
  • Debugging event messages
  • Tracking information
  • Auditing system security
  • etc.

To enable logging to Syslog, go to:

  • Navigation menu -> Syslog Configuration


The following options are available:


Determines whether messages are sent to your Syslog Server or not.


What is the address of the server running your Syslog Server?


The port used by your Syslog server.


A facility code specifies the type of program that is logging the message and allows different log sources to be handled in different ways.

Possible values are:

  • KernelMessages
  • UserLevelMessages
  • MailSystem
  • SystemDaemons
  • InternalMessages
  • LinePrinterSubsystem
  • NetworkNewsSubsystem
  • UUCPSubsystem
  • ClockDaemon1
  • ClockDaemon2
  • FTPDaemon
  • NTPSubsystem
  • LogAudit
  • LogAlert
  • SecurityOrAuthorizationMessages1
  • SecurityOrAuthorizationMessages2
  • LocalUse0
  • LocalUse1
  • LocalUse2
  • LocalUse3
  • LocalUse4
  • LocalUse5
  • LocalUse6
  • LocalUse7


In most cases one of the LocalUse values can be used for Password Server log events, or another facility value which is not used to indicate another program in your Syslog server.

Tag page
You must login to post a comment.