A.5 Logging Configuration File
You can configure common logging through the following files depending on the subsystem you want to modify.
Table A-2 Configuration File
Subsytem | File |
---|---|
Database | <OFSAAI Installed Directory> /database/ db_tools/log4j2.xml |
Scenario Manager | <OFSAAI Installed Directory>/ behavior_detection/toolkit/mantas_cfg/ install.cfg |
Behavior Detection | <OFSAAI Installed Directory>/ behavior_detection/algorithms/MTS/ mantas_cfg/install.cfg |
Alert Viewer/Administration Tools Web Server logs | $FIC_WEB_HOME/conf/RevLog4jConfig.xml <root>
The following logger levels are available:
|
Alert Viewer/Administration Tools Application Server logs |
The following logger levels are available:
|
Services | <OFSAAI Installed Directory> /services/ server/webapps/mantas/WEB-INF/log4j2.xml |
Ingestion Manager | <OFSAAI Installed Directory> /ingestion_manager/config/log4j2_common.xml |
The configuration file specifies enabling of priorities in a hierarchical fashion. For example, if Diagnostic priority is enabled, Notice, Warning, and Fatal are also enabled, but Trace is not.
- Locations of recorded log messages
- Logging to the console, files, UNIX syslog, e-mail addresses, and the Microsoft Windows Event Viewer
- Routing based on severity and/or category
- Message library location
- Maximum log file size
Monitoring Log Files
When using a tool to monitor a log file, use the message ID to search for a particular log message instead of text within the message itself. Under normal circumstances, the message IDs are not subject to change between OFSBD releases, but the text of the message can change. If a message ID does change, you can refer to the appropriate readme.txtfile for information about updated IDs.