...

• Service
  • The service is compliant to RFC5424, aka Syslog Protocol.
  • The Log Management Service offers restart capabilities: in case of fail-over or switch-over of JOC Cockpit the Log Management Service will become available from the active JOC Cockpit instance.
• Clients
  • The JS7 products, JOC Cockpit, Controller and Agents can act as clients to the Log Management Service. The products can be configured to report log output to the JS7 Log Management Service.
  • Users have a choice to enable forwarding of log output per instance of a JS7 product during installation or later on by adjusting the Log4j2 configuration. 
• User Interface
  • JOC Cockpit offers the user interface to access and to query log output.

...

• Log_server_active (Default: false)
  • Specifies that the Log Management Service is started with JOC Cockpit.
• log_server_port (Default: 4245)
  • Specifies the UDP port to which the Log Management Service will listen.
• log_server_max_messages_per_second (Default: 1000)
  • Specifies the max. number of messages per second that the Log Management Service will process.

Life Cycle

Log data created by the Log Management Service are subject to purge by the JS7 - Cleanup Service.

Users can specifiy the retention period for log data with the Cleanup Service..

Delimitation

Due to limitations of the underlying Syslog Protocol the JS7 Log Management Service does not meet elaborated requirements for security, resiĺience and high availability.

...