There is a property in the “%COLLATION_HOME%\etc\collation.properties” file that improves readability of the logs by separating the logging into per-sensor log files.
To enable this, set the following property:
If you do not set this property to true, default logging for all sensors is dumped in “%COLLATION_HOME%\log\services\DiscoveryManager.log”. This property separates the logs into the following directories: “%COLLATION_HOME%\log\sensors\<runid>\sensorName-IP.log” ex: sensors/20070621131259/SessionSensor-10.199.21.104.log The runid includes the date of the discovery run and the log file name includes the sensor name and IP address of the target. When using this option, the logs are not automatically cleared, this must be done manually, if required.
The following logging levels are valid:
Setting the logging level for the Topology JVM to DEBUG can cause performance problems on some systems. You should set the level for this JVM to DEBUG only when you need to debug storage errors or other topology issues. If a problem takes more than a few minutes to reproduce, more space should be allocated for the Topology logs. Review the following properties in the collation.properties file, and increase the values of these properties as needed:
# File size of a rollover log file com.collation.log.filesize=20MB Number of logfiles before rollover com.collation.log.filecount=5
When all the space is used as allocated by the values of these properties, the oldest data is deleted. A common setting for most issues is to set the global logging level to DEBUG and set the logging level for the Topology JVM to INFO, as shown in the following example: