Dynamic logging

Dynamic logging allows you to configure a Launcher process for logging while the Launcher is running. You can configure the following logging entries in the Management Console:

Logging Entries

• Launcher (ES)
• Resource Manager (RM)
• Connection Manager (CM)

Each logging entry is categorized by the following severity classes and debug components listed from lowest impact to highest:

Logging Categories

• Trace
• Debug
• Info
• Warn
• Error
• Fatal

Without having to stop the Launcher, you can turn each of these logging components (Trace, Debug, Info, Warn, Error and Fatal) for each of the logging entries (Launcher, Resource Manager, and Connection Manager) on and off individually for a Launcher process that you select to configure.

For example, you can run the Launcher with INFO settings to track the status of maps. If one of the maps connecting to a database starts to fail, you can dynamically enable the setting (turn on) for the DEBUG and ERROR components under the Connection Manager logging entry for a Launcher process that you have selected. Now you can track what the database connection is reporting without having to stop the Launcher, configure the Launcher with different debug settings, and then restart it.