Syslog logging

Information about using syslog to collect and store
VIP Enterprise Gateway
logs.
Although
VIP Enterprise Gateway
log files can be viewed from
Configuration Console
, it may not be a practical way to monitor the system. You can configure the syslog server as a syslog logging server to collect and store most of the
VIP Enterprise Gateway
logs. The logs are still stored in files.
By default,
VIP Enterprise Gateway
uses the LOG_LOCAL0 facility for syslog. In the default configuration, all syslogs for the LOG_LOCAL0 facility go to /var/log/messages. To configure a different location for syslogs, update the
/etc/syslog.conf
file as described:
The log levels that you configure for the
VIP Enterprise Gateway
in the
Configuration Console
override the log levels you set here.
  1. Set the syslog facility level to the same as what is set in
    VIP Enterprise Gateway
    Configuration Console
    . For example:
    local0.* /var/log/vipeg_9_8.log
    Where * indicates the levels of logging.
    Refer to the
    syslog.conf
    main page for more details on customized configurations.
  2. Send a SIGHUP signal to the syslog process.
You can use the following filters in the syslog server to categorize the logs according to
VIP Enterprise Gateway
components:
VIP Enterprise Gateway
log filters
Filters
Description
vipegconsole
To filter the logs that are related to
VIP Enterprise Gateway
console.
SSP
To filter the logs that are related to
VIP Enterprise Gateway
Self Service Portal.
VIPMGR
To filter the logs that are related to
VIP Enterprise Gateway
VIP Manager IdP.
LDAP Sync
To filter the logs that are related to
VIP Enterprise Gateway
LDAP Directory synchronization.
ValidationServer
To filter the logs that are related to
VIP Enterprise Gateway
Validation server.
JettyServer
To filter the logs that are related to
VIP Enterprise Gateway
Jetty Server logs.
If you want to get all the logs related to
VIP Enterprise Gateway
components, use all the filters that are described in
VIP Enterprise Gateway
log filters
.
Syslog supports large messages without any message truncations. You can view a unique sequence number with each individual line of syslog. This sequence number acts as the identifier for the line of log. If the message is larger than 1024 Bytes,
VIP Enterprise Gateway
splits the message in the application-level and introduces tags to identify the continuity.