Logging levels

The logging level affects how much information is included in the log files. You can set logging levels either globally or locally for each TADDM service. Use the tracectl utility to set the logging level. The new logging levels take effect within about 60 seconds of the change to the collation.properties file.

You can make and save changes to the existing logging levels in the collation.properties file without restarting the TADDM server.

Setting the logging level

To set the logging level, complete the following steps:
  1. Go to the $COLLATION_HOME/bin directory.
  2. Run the following command with your chosen values for service and level:
    ./tracectl -s service -l level
    service
    The service for which you want to set the logging level. The valid values are:
    Discover
    The service that runs sensors.
    DiscoverAdmin
    The service that stores sensor results and monitors the discovery process.
    EventsCore
    The service that performs security functions.
    Proxy
    The service that performs UI and API functions.
    Topology
    The service that handles data management, change detection, and reconciliation.
    EcmdbCore
    The EventsCore, Proxy, and Topology services on a synchronization server in a synchronization server deployment.
    DiscoveryService
    The DiscoverAdmin and Proxy services on a discovery server in a streaming server deployment.
    StorageService
    The EventsCore, Proxy, and Topology services on a primary or secondary storage server in a streaming server deployment.
    Global
    All other services that are not included by the service-specific values that are previously listed. Affected log files include tomcat.log (TADDM 7.3.0), or wlp.log (TADDM 7.3.0.1, and later), and migration.log.
    level
    The logging level that you want to use. The valid values are:
    • DEBUG
    • ERROR
    • FATAL
    • INFO
    • TRACE
    • WARN

    Notes:
    • Setting the logging level for the Topology JVM to DEBUG can cause performance problems on some systems. Set the level to DEBUG only to debug storage errors or topology issues. If the time to re-create a problem takes more than a few minutes, you must allocate more space 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.
    • Do not set the logging level to TRACE unless IBM® Support requests that you do this.

Troubleshooting problems with TADDM

To troubleshoot problems with TADDM, complete the following steps to set the logging level on the TADDM server for debugging:
  1. In the collation.properties file, set the logging level to DEBUG, as shown in the following example:
    com.collation.log.level=DEBUG
  2. Use split logging. The following properties must be set to true, which is the default value:
    com.collation.discover.engine.SplitSensorLog=true
com.ibm.cdb.topobuilder.SplitAgentLog=true
  3. Save and close the collation.properties file.
  4. Optionally, remove all files from the log directory.