Page History
...
JS7 - Log Management is offered with JOC Cockpit acting as a central point of view for monitoring of log output and dispatch of notifications created by JS7 products Controller, Agent & JOC Cockpit instances.
The Log Notification Service is available from the active JOC Cockpit instance within the scope of of JS7 - Services.
- Service
- The service is used to collect warnings and errors from log output of Controllers and Agents Controller & Agent instances and to create JS7 - Notifications. JOC Cockpit notifications are created directly and without use of the service.
- The service is compliant to RFC5424, aka Syslog Protocol.
- The service offers restart capabilities: in case of fail-over or switch-over of JOC Cockpit the Log Notification Service will become available from the active JOC Cockpit instance.
- Clients
- The JS7 Controller and Agents can & Agent instances act as clients to the Log Notification Service. The products can be configured to report warnings and errors from log output to the JS7 Log Notification Service, for details see see JS7 - Log Configuration for use with System Notifications.
- Users have a choice to enable forwarding of log output per instance of Controller and & Agent during installation or later on by adjusting the Log4j2 configuration.
- User Interface
- The JOC Cockpit offers notifications System Notifications from the JS7 - Monitor view.
- The JOC Cockpit offers JS7 - Notifications - Configuration for forwarding notifications by mail, from command line tools etc.
...
The Log Notification Service is configured with the JS7 - Settingspage.
...
| Section | Setting | Default Value | Required | Purpose |
|---|---|---|---|---|
lognotification |
log_server_active | false | no | Specifies that the Log Notification Service is started with JOC Cockpit. | |
| 4245 | no | Specifies the UDP port to which the Log Notification Service will listen. | |
| 1000 | no | Specifies the max. number of messages per second that the Log Notification Service will process. |
Delimitation
Due to limitations of the underlying Syslog Protocol the JS7 Log Notification Service does not meet elaborated requirements for security, resiĺience and high availability.
...
- This allows the service to switch from a current JOC Cockpit instance to the next active JOC Cockpit instance.
- Switching to a different host operating the active JOC Cockpit instance includes that the hostname of the Log Notification Service will change.
- Users can apply a FailoverAppender with the JS7 - Log Configuration for use with System Notifications to switch between JOC Cockpit instances in case of unavailability.
- Users can set up a Proxy Service that will forward log messages to the currently active JOC Cockpit instance.
If no JOC Cockpit instance is active, then no log messages can be picked up:
...
Overview
Content Tools