Configuring remote logging

[Version 8.6 and later]You can enable remote logging to save log entries on a remote server. Remote logging can be helpful when you must set a detailed debugging log level to help isolate a problem or monitor behavior over a long time period.

Before you begin

  • You must have a syslog server available to listen for and capture events.
  • The names of your catalog servers, container servers, and application servers (if you are using WebSphere® Application Server) must contain alphanumeric characters only. Syslog RFC 1364 does not allow non-alphanumeric characters for the TAG field. The TAG field contains the server name in the syslog messages.

About this task

Use remote logging for analysis of historical data. The servers in your environment keep a limited number of log files in the system. Configure remote logging if you require more log files to be saved for further analysis. The remote logging server aggregates the data from multiple servers. You can configure your entire topology of catalog servers and container servers to send files to the same remote logging server.

Procedure

  1. Configure remote logging on each catalog server or container server.
    Enable remote logging by editing the following properties in the server properties file:
    [Version 8.6 and later]syslogEnabled
    [Version 8.6 and later]Enables remote logging for analysis of historical data. You must have a syslog server available to listen for and capture events.

    Default: false

    [Version 8.6 and later]syslogHostName
    [Version 8.6 and later]Specifies the host name or IP address of the remote server on which you want to log historical data.
    [Version 8.6 and later]syslogHostPort
    [Version 8.6 and later]Specifies the port number of the remote server on which you want to log historical data.

    Valid values: 0-65535

    Default: 512

    [Version 8.6 and later]syslogFacility
    [Version 8.6 and later]Indicates the type of remote logging facility that is being used.

    Valid values: kern, user, mail, daemon, auth, syslog, lpr, news, uucp, cron, authpriv, ftp, sys0, sys1, sys2, sys3,local0, local1, local2, local3, local4, local5, local6, local7

    Default: user

    [Version 8.6 and later]syslogThreshold
    [Version 8.6 and later]Specifies the threshold of the severity of messages that you want to send to the remote logging server. To send both warning and severe messages, enter a value of WARNING. To send severe messages only, enter SEVERE.

    Valid values: SEVERE, WARNING

    Default: WARNING

  2. Restart the catalog servers and container servers on which you changed the properties.
    For more information, see Starting and stopping stand-alone servers.

Results

Messages are sent to your configured remote logging server for archival and analysis.