Define the policies for log and trace information generated on clients for the selected application. You can download and view client log files. Trace information is generated as part of an end-to-end trace session.
Client log and trace policies are propagated to the client. Clients must adhere to the policies. For example, clients must delete logs based on the defined time period.
The log and trace policies specified here apply to all application registrations. These settings can be overridden for a specific registration by the log and trace policies defined at the registration level.
|Path||For tracing execution flow. Used, for example, in the context of entering and leaving a method, looping, and branching operations. (Not applicable to the offline logging component.)|
|Debug||For debugging purposes, includes extensive and low-level information.|
|Info||Informational text, used mostly for echoing what has been performed.|
|Warn||The application can recover from the anomaly, and fulfill the task, but requires attention from the developer or operator.|
|Error||The application can recover from the error, but cannot fulfill the task due to the error.|
|Fatal||The application cannot recover from the error, and the severe situation causes fatal termination.|
|None||No trace information is collected. Use this level when performing analysis on the client.|
|Low||Collects trace information related to response time distribution. Use this level to analyze the amount of time spent on each server component.|
|Medium||Collects trace information related to performance. This trace level corresponds to the Info log level setting. During a trace session, this level overrides a lower log setting to increase the amount of information logged.|
|High||Collects detailed functional logging and tracing information. This trace level corresponds to the Debug log level setting. During a trace session, this level overrides a lower log level to increase the amount of information logged.|