Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • Service
  • Clients
    • Controller and Agents can act as clients to the Log Management Notification Service. The products can be configured to report warnings and errors and warnings to the Log Management Notification Service.
    • Users have a choice to enable forwarding of log output warnings and errors during installation or later on by adjusting the Log4j configuration.

...

By default the Log4j configuration of Controller and Agents will not make use of the Log Management Notification Service. Instead, users choose for which instances of Controllers and Agents they want to send errors and warnings to the Log Management Notification Service.

The following examples explain the Log4j configuration.

...

  • <Syslog>: The XML element holds the required configuration. The following attributes are available:
    • name: users a free to choose a name for the Syslog Appender.
    • format: The value RFC5424 is required.
    • host: The hostname or IP address of JOC Cockpit operating the Log Management Notification Service.
    • port: The port to which the  Log Management Notificatio Service listens.
    • protocol: The value UDP is required.
    • charset: The value UTF-8 is required.
    • facility: The value LOCAL0 is required
    • newLine: The value false is required.
  • <PatternLayout>: The XML element specifies the pattern used to send messages. The pattern must not be changed.

...