Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Navigation
Guide That Contains This Content
[+] Expand All
[-] Collapse All

    Configuring Event Logging for an SIC Server (SRC CLI)

    You can configure the SIC server to capture any number of log streams called loggers. If you configure multiple log streams, make sure you configure unique names for each log stream. You can configure the log stream to display only log messages from particular log groups. To configure the event level for a log group, you first specify the log group and then specify the event level for it.

    Use the following statements to configure event logging for the SIC server:

    shared sic group identifier server identifier
    shared sic group identifier server identifier logger id
    shared sic group identifier server identifier logger id file { filter (/error | /debug-error); filename filename; maximum-file-size maximum-file-size; rollover-interval rollover-interval; rollover-on-startup; flush-after-writes; high-resolution-timestamps; header header; footer footer; prepend-message-header; work-id-label work-id-label; work-id-padding work-id-padding; utc; }
    shared sic group identifier server identifier logger id group (administration | audit | configuration | system | packet | packet-trace | packet-trace-raw) { events (error | warning | standard | detail | debug); }

    To configure event logging for the SIC server:

    1. From configuration mode, access the statement that configures the server belonging to the SIC group. For example, to configure the server called sicser1 for the group group1:
      [edit]user@host# edit shared sic group group1 server sicser1
    2. Specify the name used by the server to identify the log stream.
      [edit shared sic group group1 server sicser1 logger]user@host# set id log1
    3. (Optional) Specify the filter to define which event messages are logged or ignored.
      [edit shared sic group group1 server sicser1 logger log1 file]user@host# set filter (/error | /debug-error)

      where:

      • /error—Error events are captured for every log group
      • /debug-error—Debug events are captured for every log group
    4. Specify the prefix to be added to the log file for easy identification.
      [edit shared sic group group1 server sicser1 logger log1 file]user@host# set filename filename
    5. (Optional) Specify the maximum size of the log file and the rollover file.
      [edit shared sic group group1 server sicser1 logger log1 file]user@host# set maximum-file-size maximum-file-size

      Note: The maximum file size is specified in KB. Maximum size of the log file is 10,000,000 KB.

      Do not set the maximum file size to a value greater than the available disk space.

    6. (Optional) Specify the time in seconds for the rollover interval after which the new log file is created.
      [edit shared sic group group1 server sicser1 logger log1 file]user@host# set rollover-interval rollover-interval
    7. (Optional) Specify whether the new log file is to be created every time the server starts.
      [edit shared sic group group1 server sicser1 logger log1 file]user@host# set rollover-on-startup
    8. (Optional) Specify whether or not to buffer log messages.
      [edit shared sic group group1 server sicser1 logger log1 file]user@host# set flush-after-writes
      • If set, log messages are immediately written to the log file without buffering. Use this setting for real-time logging.
      • If not set, SIC log messages are kept in the buffer until the buffer is full and then all messages in the buffer are written to the log file. Use this setting for performance optimization, when real-time logging is not needed.
    9. (Optional) Specify whether the high-resolution-time reporting system functions are used.
      [edit shared sic group group1 server sicser1 logger log1 file]user@host# set high-resolution-timestamps
    10. (Optional) Specify the header message to be added to the beginning of each log file.
      [edit shared sic group group1 server sicser1 logger log1 file]user@host# set header header
    11. (Optional) Specify the footer message to be added to the end of each log file.
      [edit shared sic group group1 server sicser1 logger log1 file]user@host# set footer footer
    12. (Optional) Specify whether to prepend each log message with additional information such as time, thread, and transaction information.
      [edit shared sic group group1 server sicser1 logger log1 file]user@host# set prepend-message-header
    13. (Optional) Specify the work data ID prefix to be added to each log message.
      [edit shared sic group group1 server sicser1 logger log1 file]user@host# set work-id-label work-id-label
    14. (Optional) Specify the string to be added to each log message if work data is not available.
      [edit shared sic group group1 server sicser1 logger log1 file]user@host# set work-id-padding work-id-padding
    15. (Optional) Specify the time and date values to Universal Time Coordinates (UTC, formerly known as Greenwich Mean Time, or GMT). If disabled, time and date reflect local time.
      [edit shared sic group group1 server sicser1 logger log1 file]user@host# set utc
    16. Configure the event level for each log group for which you want to collect events. First, specify the name of the log group, and then specify the event level. Repeat the process for each log group for which you want to collect events.
      [edit]user@host# edit shared sic group group1 server sicser1 logger log1 group (administration | configuration | system | packet | packet-trace | packet-trace-raw)

      Where:

      • administration—Log group reports events related to server administration.
      • audit—Log group reports SSR database operations (insert, update, and delete operations) for both the user session and the corresponding operations in the service session table.
      • configuration—Log group reports events related to server configuration.
      • system—Log group reports events related to the system, such as system start and system stop.
      • packet—Log group reports events related to transaction processing, such as incoming and outgoing packets.
      • packet-trace—Log group displays contents of a packet. The format is attribute name:attribute value.
      • packet-trace-raw—Log group displays raw data (octets) of incoming and outgoing packets.

      Note: To write SSR database operation information to a new file, you must configure a new logger and specify only audit in the group.

    17. (Optional) Specify the highest event level for the log group.
      [edit shared sic group group1 server sicser1 logger log1 group]user@host# set events (error | warning | standard | detail | debug)

      Where:

      • error—Messages in log shown at event level error.
      • warning—Messages in log shown at event levels error and warning.
      • standard—Messages in log shown at event levels error, warning, and standard.
      • detail—Messages in log shown at event levels error, warning, standard, and detail.
      • debug—Messages in log shown at event levels error, warning, standard, detail, and debug.

    Modified: 2014-06-11