Configuring Log Levels
You can configure the log level settings to specify the level of detail that you want to capture in the logs.
The log level settings that you can specify are described below. Each logging level includes the indicated type of message and all messages from the levels above it (for example, the Warn level includes Fatal, Error, and Warn messages).
Log Level | webMethods API Gateway Server records these entries | Examples |
---|---|---|
Fatal | Failures that end operations in such a way that the operations cannot successfully continue without user intervention. Failure is very likely to affect other operations or products. | Product cannot read its configuration file and has no default settings. |
Error | Same as Fatal, except that existing error handling renders the failure unlikely to affect other operations or products. | Business process step failed due to a service error caused by bad input data. |
Warn | Problems that do not end operations, or unexpected or unusual conditions that might signal impending failure. | Multiple registered JMX servers were discovered where only one is needed. |
Info | Success of an event that you need to know about. | Package was loaded, or connection was pool initialized. |
Debug | Code-level statements recording unusual conditions or decisions that might lead to errors. | Expects an object to be initialized but it is not, or hash table is empty. |
Trace | Code-level statements recording the state and flow of the program during normal execution. | Entry or exit method, or local and global object state. |
Off | No information for the product or facility is written to the server log. |
Prerequisite:You must have the Manage general administration configurations functional privilege to configure log levels.
To configure log levels