Tracing Options

The Tracing Options configure how Studio and/or Runtime/Agile Desktop outputs diagnostic messages using the Trace Publisher. For information, see Diagnostics Configuration.

This topic describes the configuration options for the Trace publisher:

Trace Level
Trace Output
Trace Source

Note: Use the Trace publisher under advisement of Support.

Trace Level

The Trace Level options set nature of the tracked events reported. The levels are described here:

Note: Each level stacks messages appropriate to all levels above. For example, selecting Verbose includes Information, Warning, Error, and Critical messages. When applying the trace level and the log level for the selected log categories (Studio or Runtime/Agile Desktop), the most restrictive level is used. For example, if the log level for a category is set to Error and the trace level is set to Verbose, only error level messages are generated.

Level	Type of tracked events
Critical (0)	This setting records negative events which indicate unexpected processing or an error. Only certain unhandled exceptions are reported.
Error (1)	This setting records error messages, indicating the application was not able to perform a task as expected. The application is, however, still running.
Warning (2)	This setting records both error and warning messages.
Info (3)	This setting records error, warning, and informational messages. It includes successful milestones of application execution, regardless of whether the application is working properly, and provides an overview of what happened.
Verbose (4)	This setting records error, warning, informational messages and verbose debugging output. Note: This option generates a large number of messages and is not recommended when used with multiple trace source selections.

Trace Output

The Trace Output options are:

All
Console
Debugger
SuperTrace

Note that the out options may require addition configuration. For example, the SuperTrace output option contains settings in the openspan.ini file which define how the trace log files are managed.

Trace Source

The Trace Source options list the modules from which trace messages may be output. The sources can be any combination of the Available Trace Sources listed below. Example sources:

Broker, BrokerHook, BrokerInit, BrokerSubclass: Log functions in the windows broker
External: Logs from all translators (the names of the translators are included in the messages)

Note: The level and the source selected for tracing affect performance. For example, selecting Verbose as the trace level and All as the trace source can seriously degrade application performance.

Available Trace Sources

All
Adapters
Broker
BrokerHook
BrokerInit
BrokerSubclass
CitrixDriver
Debug
Exceptions
External
Framework
Function
Heaps
Hooking
Initialization
Injection
Instruction
Interop
IPC
Matching
Modules
Pebs
Process
Security
Service
SharedMemory
Tracing
Web
Windows