Open topic with navigation

TIBCO ActiveSpaces® 4.8.0

# Log Levels

The log level determines the level of detail and the quantity of log statements. Typically, log levels must not be adjusted because producing excess log output can affect performance. However, there are situations such as debugging an issue where different log levels must be configured.

ActiveSpaces uses the logging mechanism provided by TIBCO FTL. For more information, see "Log Levels" in TIBCO FTL® Development.

The tibdg client library as well as the tibdgkeeper, tibdgproxy, and tibdgnode process can all be configured with nondefault log levels. The client library has an API used to set the log level. The data grid processes can be configured by using the `-t` command-line parameter. The log levels are set by using one of the following forms:

    element:level

or

    element:level;element:level;element:level

Often, additional debug log statements can be gathered by using `tibdg:debug` as the log level. The output of this command shows more log statements than the default log level (`tibdg:info`). The specific syntax when used with the tibdgproxy data grid process would be:

    tibdgproxy -r http://realm_url:port -t tibdg:debug -n p_01

Other log levels or elements might be requested to be set when investigating specific issues as needed.

You can use the logs to trace client API calls on a thread basis. To trace the calls, use the client API to set the log level to `tibdgapi:debug3`. This triggers the client library to produce log statements for calls to API functions.

Copyright © 2009-2022. Cloud Software Group, Inc. All Rights Reserved.