Introduction
JS7 allows Log Management with JOC Cockpit offering a central view for monitoring of log output created by JS7 products.
- Service
- The JS7 - Log Management Service is compliant to RFC5424, aka Syslog Protocol.
- The Log Management Service is available from JOC Cockpit within the scope of JS7 - Services.
- 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 Log Management Service.
- In addition, log output of JS7 products is always written to local log files.
- 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.
The JS7 Log Management Service becomes available from
- JOC-1828Getting issue details... STATUS
FEATURE AVAILABILITY STARTING FROM RELEASE 2.7.2
Log4j2 Configuration
By default the Log4j configuration of JS7 products will not make use of the Log Management Service. Instead, users choose for which instances of JS7 products they want to send log output to the Log Management Service.
Controller Log4j2 Configuration
The following Log4j2 configuration is available from the log4j2.xml-example
file in the Controller's <controller-data>/config
directory:
Explanations:
- tbd
Agent Log4j2 Configuration
The following Log4j2 configuration is available from the log4j2.xml-example
file in the Agent's <agent-data>/config
directory:
Explanations:
- tbd
JOC Cockpit Log4j2 Configuration
The following Log4j2 configuration is available from the log4j2.xml-example
file in the JOC Cockpit's <jetty-base>/resources/joc
directory:
Explanations:
- tbd