Collecting Data: How to setup general DEBUG logging in TADDM

Answer

Refer to the appropriate sections below to set DEBUG for your TADDM environment.

	What you need to know about DEBUG logging
	Setting DEBUG for TADDM 7.2.1 and later, Streaming mode
	Setting DEBUG for TADDM 7.2.1 and later, Domain or Enterprise MODE
	Setting DEBUG for TADDM 7.2.0

What you need to know about DEBUG logging

1. If possible, stop TADDM, clear the log directory and restart TADDM to gather clean logs of the problem, this can make diagnosis faster if the logs contain only data of the problem being reported. Additionally this will limit the size of data to be sent which can save you time.

2. If the problem reported requires logs over a large amount of time, adjust the collation.properties settings:

com.collation.log.filecount
com.collation.log.filesize

as needed to ensure logs are gathered for the entire time frame. Ensure enough space is available on the server to gather this many logs. Changes to these properties require a restart of TADDM to be effective. Do not use excessively large settings, such as over 100 files or size over 40M. Set the properties back to default values when complete to avoid logger hangs.

3. Existing log.level properties change dynamically within 5 minutes, a restart of TADDM is not generally required if updating an existing log.level property. An exception to this is com.collation.log.level.vm.Anchor, this setting is not typically dynamic unless also changed on the anchor.

4. The settings in this technote are general settings. More details settings may be required for certain problem types. Refer to the specific must gather documentation for the problem you are experiencing to determine if any other log settings are required.

5. For details on what each JVM is responsible for, refer to the TADDM Troubleshooting Guide at:

http://www.ibm.com/support/knowledgecenter/en/SSPLFC_7.3.0/com.ibm.taddm.doc_7.3/TSGuide/c_cmdb_logging_levels.html

<top>

Setting DEBUG for TADDM 7.2.1 and later, Streaming mode

You are running in this mode when collation.properties contains:

com.collation.taddm.mode=DiscoveryServer or StorageServer

The following collation.properties log level settings apply to TADDM Streaming mode:

Storage Server:

com.collation.log.level=DEBUG (this applies to JVMs/scripts NOT covered by the below settings)
com.collation.log.level.vm.StorageService=DEBUG

Discovery Server:
com.collation.log.level=DEBUG (this applies to JVMs/scripts NOT covered by the below settings)
com.collation.log.level.vm.Discover=DEBUG
com.collation.log.level.vm.DiscoveryService=DEBUG
com.collation.log.level.vm.Anchor=DEBUG

You can update the properties directly within the file or use the tracectl/tracectl.bat script in dist/bin to update them:

On the Discovery Server:
./tracectl -s Discover -l DEBUG
./tracectl -s DiscoveryService -l DEBUG
./tracectl -s Global -l DEBUG

On the Storage Server:
./tracectl -s StorageService -l DEBUG
./tracectl -s Global -l DEBUG

Note that the anchor setting is only modifiable in collation.properties. It must also be updated on the remote anchor if such exists.

<top>

Setting DEBUG for TADDM 7.2.1 and later, Domain or Enterprise mode

You are running in this mode when collation.properties contains:

com.collation.cmdbmode=domain or enterprise

The following collation.properties log level settings apply to TADDM DOMAIN or Enterprise mode:

com.collation.log.level=DEBUG (this applies to JVMs/scripts NOT covered by the below settings)
com.collation.log.level.vm.Topology=DEBUG
com.collation.log.level.vm.Discover=DEBUG
com.collation.log.level.vm.EventsCore=DEBUG
com.collation.log.level.vm.Proxy=DEBUG
com.collation.log.level.vm.EcmdbCore=DEBUG
com.collation.log.level.vm.DiscoverAdmin=DEBUG
com.collation.log.level.vm.Anchor=DEBUG

You can update the properties directly within the file or use the tracectl/tracectl.bat script in dist/bin to update them:

./tracectl -s Global -l DEBUG
./tracectl -s Topology -l DEBUG
./tracectl -s Discover -l DEBUG
./tracectl -s EventsCore -l DEBUG
./tracectl -s Proxy -l DEBUG
./tracectl -s EcmdbCore -l DEBUG
./tracectl -s DiscoverAdmin -l DEBUG


Note that the anchor setting is only modifiable in collation.properties. It must also be updated on the remote anchor if such exists.


<top>

Setting DEBUG for TADDM 7.2.0

In TADDM 7.2.0, typically only one log.level setting exists in collation.properties, set this to DEBUG:

com.collation.log.level=DEBUG

If you find other log.level setting for individual JVMs, which may of been added after installation, for example:

com.collation.log.level.vm.Topology

Change those to DEBUG as well.


<top>