 | ||
| LogDbg | ||
|---|---|---|
| Prev | Static type attribute definitions | Next |
The LogDbg attribute indicates the debug severities enabled for the resource type or agent framework.
Debug severities used by agent functions are in the range of DBG_1 - DBG_21. By default, LogDbg is an empty list, meaning that no debug messages are logged for a resource type. Users can modify this attribute for a given resource type, to specify the debug severities that they want to enable, which would cause those debug messages to be printed to the log files. For more information on agent debug levels, see the Cluster Server Bundled Agents Reference Guide.
The LogDbg attribute can be overridden at a resource level.
The debug messages from the agent framework are logged with the following severities:
DBG_AGDEBUG: Enables most debug logs.
DBG_AGINFO: Enables debugging messages related to specific entry-point execution.
DBG_AGTRACE: Enables verbose debug logging that prints function tracing.
See Using debug messages.
More information is available about APIs that are available to log debug messages from agent entry points.
See About logging agent messages.
These APIs expect a debug severity as a parameter, along with the message to be logged. You can choose different debug severities for messages to provide different logging levels for the agent. When you enable a a particular severity in the LogDbg attribute, agent entry points log corresponding messages.
The LogDbg attribute is modified such that it can be overridden in VCS 6.2 or later releases. Although using this attribute, we can set DBG_AGINFO, DBG_AGTRACE, DBG_AGDEBUG at resource level but they will not have any impact as these levels are agent type specific. Hence we recommend to set values between DBG_1 to DBG_21 at resource level using this attribute.