Manage log levels

Zilliant CPQ provides robust log management capabilities that allow you to define log levels for the application logs. Log levels identify the severity of events, enabling you to separate informational messages from those that indicate potential problems or critical errors.

Define log levels to control the detail of data that your logs record. This helps ensure that you receive only relevant and necessary information about system events to simplify monitoring and troubleshooting.

To define log levels:

1. From the application left navigation area, select Administration.

2. From the top navigation bar, select Logging Configuration.

3. Locate a row with the package or class name for a log.

4. On the row, from the dropdown list in the Log Level column, select a log level:

   • OFF—Disables the log.
   • ERROR—Records issues that hinder the execution of specific operations. In this state, the application may still function, but with limited functionality or degraded performance. This log level highlights issues that require immediate investigation.
   • WARN—Records warnings about unexpected situations that could lead to future problems. In this state, the application continues to function normally.
   • INFO—Records routine events significant to the application's business purpose, such as user actions or system updates. These log records confirm that the system is operating as expected.
   • DEBUG—Records detailed information to help developers identify and diagnose issues during debugging or troubleshooting.
   • TRACE—Records the most detailed logs by tracing the step-by-step execution of code in the application. It provides a complete breakdown of the events leading to a problem or a significant system event.
   • ALL—Records all events, regardless of severity.
   Note

   The selected log level can impact system performance. For example, higher levels like DEBUG and TRACE capture detailed information, which requires more processing and additional resources. This may slow down the system. Use these levels sparingly, mainly for troubleshooting or debugging.