Page History
...
JS7 offers Log Management with JOC Cockpit acting as a central point of view for monitoring of log output and dispatch of notifications created by Controller, Agents & JOC Cockpit , Controller and Agentsinstances.
- JS7 - Notifications from Logs
- Service
- The JS7 - Log Notification Service is used to collect warnings and errors from log output of Controller and Agents& Agent instances. JOC Cockpit notifications are created directly and without use of the service.
- The service is compliant to RFC5424, aka Syslog Protocol and offers restart capabilities.
- Clients
- The JS7 Controller and Agents & Agent instances can act as clients to the Log Notification Service. The products can be configured to report log output to the Log Notification Service, for details see JS7 - Log Configuration for use with System Notifications
- Users have a choice to enable forwarding of log output per instance of a Controller or & Agent during installation or later on by adjusting the Log4j 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.
- Service
- Access to Logs
- The JOC Cockpit offers near real-time access to logs of distant Controllers Controller and AgentsAgent instances.
- Log Replication is offered to store logs to a central location.
...
The JS7 - Log Notification Service is is available from the active JOC Cockpit instance within the scope of of JS7 - Services.
The service creates notifications from warnings and errors of Controllers and Agents. Controller & Agent instances.
Clients
By default the Log4j configuration of JS7 Controller and Agents & Agent instances will not make use of the Log Notification Service. Instead, users choose for which instances of Controller and Agents JS7 products they want to send log output forward warnings and errors to the Log Notification Service.
...
Overview
Content Tools