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.

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.

Problems that do not end operations, or unexpected or unusual conditions that might signal impending failure.

Multiple registered JMX servers were discovered when only one is needed.

Success of an event that you need to know about.

Package loaded, or connection pool initialized.

Code-level statements recording unusual conditions or decisions that might lead to errors.

Expected an object to be initialized but it is not, or hash table is empty.

Code-level statements recording program flow and state during normal execution.

Method entry/exit, or local and global object state.

No information for the product or facility is written to the server log.

This setting sets the API Gateway server log level. All the design time activities (such as creation of API,application, alias, and so on) and run-time activities (such as API invocation) are logged based on this setting. API Gateway server logs also contain information on the start-up activity of API Gateway server and its functioning, its state and activities related to connections to various components.

Select a log level that you want to configure to collect required logs.

The available log levels are: off, trace, debug, info, warn, error, fatal.

By default, the log level for API Gateway server logs are set as info.

This setting sets the API Data Store log level. This contains log files of Elasticsearch bundled with API Gateway. All API Gateway assets such as API, application, alias, and so on that are stored in API Data Store are logged based on this settings.

Select a log level that you want to configure to collect required logs.

The available log levels are: off, debug, info, warn, error, fatal.

By default, the log level for API Data Store logs are set as info.

This setting sets the log level for dashboard logs. These logs contain information regarding dashboard related activities and the kibana log files that are included in API Gateway.

Select a log level that you want to configure to collect required logs.

The available log levels are: silent, quiet, verbose.

By default, the log level for dashboard logs are set as quiet.

This setting enables API Gateway security logs. These logs contain information on security-related administrative and operational events. For example, changes to authorization, authentication, port settings, password restrictions, attempts to log on to API Gateway and to access API Gateway services, and so on.

Select the checkbox to enable the collection of security logs.

This setting enables API Gateway session logs. These logs contain information on sessions activated on API Gateway and provide data on when sessions start, their current status, their duration, and so on.

Select the checkbox to enable the collection of session logs.

This setting sets API Gateway platform logs.

Select a log level that you want to configure to collect required logs.

The available log levels are: off, trace, debug, info, warn, error, fatal.

By default, the log level for platform logs are set as info.