Description

Some of the bundled VCS agents (C++) and later have been developed with the VCSAG_LOGDBG_MSG facility.
Such agents can log extra debug messages (to an agent log file) if the relevant debug level (DBG_1 to DBG_21) has been set.

If VCSAG_LOGDBG_MSG is utilized, then adding additional tags can be useful to troubleshoot customer issues.
This additional debug logging can be enabled with the halog command.

The tag values should be those that are used in the agent related scripts (online, monitor, offline, clean ), i.e. if 1 & 2 are used.
There appears to be no harm if additional tag numbers are added and the debug for a particular agent does not use them.

For example, to enable debug logging for the Application resource type, debug level 4 has to be set:

# haconf -makerw
# hatype -modify Application LogDbg -add DBG_4 DBG_AGDEBUG DBG_AGINFO
# halog -addtags 1 2 3 4
# haconf -dump -makero

The current setting for LogDbg can be displayed with:
# hatype -display resource_type | grep LogDbg

The current setting for the added tags can be displayed with:
# halog -info

To disable this feature remove the LogDbg level, and the added tags.
# haconf -makerw
# hatype -modify Application LogDbg -delete DBG_4 DBG_AGDEBUG DBG_AGINFO
# halog -deltags 1 2 3 4
# haconf -dump -makero

The following table shows some of the agent debug levels that may be useful to troubleshoot customer issues.

This document can be expanded to include other Agents for completeness.