TADDM Sensor Logging

by bluemedora_editor on May 25, 2011

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:

com.collation.discover.engine.SplitSensorLog=true

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.

Logging levels

The following logging levels are valid:

  • FATAL (log only fatal messages -> MINIMUM LOGGING)
  • ERROR
  • WARN
  • INFO (default)
  • DEBUG
  • TRACE (log every message -> MAXIMUM LOGGING)

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:

com.collation.log.level=DEBUG                                     com.collation.log.level.vm.Topology=INFO

General Heuristics:

  • Trace – Only when one would be “tracing” the code and trying to find one part of a function specifically.
  • Debug – Information that is diagnostically helpful to people other than developers (IT, sysadmins, etc).
  • Info – Generally useful information to log (service start/stop, configuration assumptions, etc). This is TADDM’s default logging level.
  • Warn – Anything that can potentially cause application oddities, but for which the program can automatically recover from (switching from a primary to backup server, retrying an operation, missing secondary data, etc).
  • Error – Any error which is fatal to the operation but not the service or application (cant open a required file, missing data, etc). These errors will force user (administrator, or direct user) intervention. These are usually reserved for incorrect connection strings, missing services, etc.
  • Fatal – Any error that is forcing a shutdown of the service or application to prevent data loss (or further data loss). Reserve these only for the most heinous errors and situations where there is guaranteed to have been data corruption or loss.

 

Get started

Try BindPlane for free. No credit card required.

Sign up
True Visibility
BindPlane for VMware vRealize Operations

True Visibility allows cloud management teams to use VMware vRealize’s powerful machine learning and capacity planning engine across their entire hybrid cloud environment.

Azure Monitor...everything
BindPlane for Microsoft Azure Monitor

Make Azure Monitor your first-pane-of-glass across your entire multi-cloud, multi-database or hybrid platform environment.

Thank you for contacting us. Your information was received. We'll be in touch shortly.