edgeCore and the underlying web application server (Apache Tomcat) produce a number of log files which can be used to monitor the operation of the product and for diagnosing issues. Most of the log files are in the [INSTALL_HOME]/logs/ directory and are automatically configured to be rotated and compressed to avoid run-away disk usage. The table below summarizes each log file and the information contained within:
By default this log file is set to the INFO level.
By default this log file is set to the INFO level and modified on a per-feed basis as mentioned above. It is possible to configure the entire edgeWeb component to DEBUG or TRACE level if needed.
Currently none of the configuration files below are user serviceable. These are system shipped files and are not backed up or restored. Changes can be made on a system if need or at the direction of support but be aware these changes will be lost if deploying a new install.
In addition to daily rotation, compression, and deletion of older files, logs managed with log4j have a further mechanism to force rotation and compression if the log size exceeds 250MB. This will allow up to a maximum of 4 rotations per day. See the SizeBasedTriggeringPolicy property in the configuration files to change this default behaviour.
By default, audit and session logging information is stored both in the log files noted above as well as the auth database. The two tables into which the information is stored are EDGE_AUDIT_LOG and EDGE_SESSION_LOG. To customize the logging activity, the following properties can be added to custom.properties.
Note that previous versions of edgeSuite used db.config.audit.rollover.count (an integer value) and db.config.audit.rollover.unit, the latter of which supported SECOND, MINUTE, HOUR, and DAY as options. If these legacy settings exist in custom.properties, they will be used, provided they amount to a time greater than or equal to 1 day. Any values less than that will be ignored and 1 day will be used.