A dedicated Log Service is available for:
- Console Standalone mode - one Log Service for the embedded Node
- Node Service (for Enterprise mode) - i.e. if you have multiple Nodes and you want each Node to benefit from the Log Service, you should install the Log Service on each Node.
Its purpose is to remove the log management complexity from Console itself, optimize the parsing and analysis of log files, alert users about specific messages found during the analysis by the Node, and format each log file output regardless of its origin into a single simple format.
The Log Service is currently in beta and is available in ≥ 2.7.
The Log Service is provided with the following installers and is installed by ticking the option highlighted below (this option is NOT ticked by default):
- AIP-Node-<version>.jar (provided in https://extend.castsoftware.com/#/extension?id=com.castsoftware.aip.console&version=latest):
- AIP-Console-Standalone-<version>.jar (provided in https://extend.castsoftware.com/#/extension?id=com.castsoftware.aip.console.standalone&version=latest):
What is installed?
The Log Service is installed:
- as a dedicated Microsoft Windows service
- set to start-up automatically
- running with the Local Service account
- running on port 8180
The following properties files contain the Log Service configuration parameters (depending on your deployment mode):
The following section controls the Log Service:
You must ensure that the Log Service Windows Service is "running" when this key is set to
Starting 2.10 any custom patterns defined as described below will be ignored. Instead alert patterns are now available in the UI, see: Administration Center - Settings - Alert Settings. If you have configured custom patterns in this way in previous releases, CAST highly recommends that you retain them before upgrading to ≥ 2.10.
This key is not visible by default, however, by manually adding it in, it allows you to configure a list of specific log messages (or parts of log messages) that the log service should watch for while processing the logs. These log messages are then highlighted in Console whenever the Log Service "sees" them in any log files it is parsing.
For example, the following could be added:
In the example below, the log message "JAVA124:Cannot resolve" has been identified by the Log Service and is highlighted in the alert/warning panel in the top right corner of Console
Behaviour during Job Execution
When the Log Service is enabled, the Node will send a request to the Log Service to monitor the main log of a Job Execution step, and then find additional logs to parse and analyze. This is mostly transparent and the log will still be visible in the Console log viewer in real time. The format for each log however changes to a more readable format and is kept coherent across different sub-processes run during an application analysis.
You must ensure that the Log Service Windows Service is "running" when the
enabled key in the .yml file is set to
true otherwise all jobs handled by the Node will fail.
If the Log Service is installed and enabled in the relevant .yml configuration file, but the Windows Service itself is stopped or has crashed, a System Alert will be displayed in CAST Console to alert you that an issue exists:
Disabling the Log Service
If you have installed an enabled the Log Service but wish to revert back to the initial log management provided by Console itself, update the
application-standalone.yml file, set the
enabled key to
false and then restart the associated Node. You may also wish to:
- stop the running Windows Service to release resources
- and/or remove the Windows Service by running the following batch file depending on your deployment mode:
Installing the Log Service manually
If you have chosen not to install the Log Service during the installation process, but wish to use it, you will need to proceed as follows:
- First manually install the Windows Service using the following batch file depending on your deployment mode:
If you do not wish to install the Log Service as a Windows Service, you can manually start the log service using the following file:
- Then update the following files depending on your deployment mode to set the
enabledkey in the
- Finally restart the Node to ensure the Log Service is fully enabled.