Temporarily changing logging events in log files
Temporarily change the logging events that are displayed in log files across all nodes in the system by modifying the log level and filter criteria for log categories.
Changing the logging events and event details that appear in the log file is helpful when testing new areas of functionality in your application, debugging your application, or for general troubleshooting of your system.
For example, you can change the logging level for activities in the Work- class from ERROR to DEBUG for troubleshooting purposes.
When you change the logging level, the system adds an entry in the Pega log that includes your operator ID and the date and time of the change. Logging level changes take effect immediately and remain in effect until the level is reset, either automatically or manually.
Log messages that are generated by the Log-Message method statement and oLog() calls in Java steps are written to the log files. The log message level for a particular message is determined by your code. The logging level that you set when you change the log level determines which messages are written to the log file.
Logging levels
Each level causes messages of that level and above to be written to the log file. For a list of the log levels, see Log levels for log categories.
For example, if the logging level is set to ERROR, log messages with a severity of ERROR and FATAL are written to the log file.
Rulesets, class hierarchy, and loggers
A logging level can be set for a specific Java class or other logger category. Rulesets and Pega Platform class hierarchy are not relevant to logging. If you set logging events for an activity named Data-Party.Research and your system includes several activities of that name (in various rulesets and versions), if any of these activities are run on the current node, they might produce logged events.
Operations on log categories require the following privileges:pzLogLevelObserver to view log categories.pzLogLevelAdministrator to edit log categories. The changes that you make are cluster-wide and persist until you change them. In the navigation pane of , click ResourcesLog categories. Click the Actions menu icon, and then click Change log level.From the drop-down list, select the log level that you want to apply to your log category.Click Submit. The new log level is displayed in the Current log level column.
- Modifying the log level and filter criteria for a log category
Temporarily modify the messages that appear in the log file by changing the log level and filter criteria of a log category. For example, you can change the logging level for activities in the Work- class from ERROR to DEBUG for troubleshooting purposes.
- Restoring log level default values
You can restore the default log levels of all your custom categories at once by resetting their log levels.
Previous topic Log levels for log categories Next topic Modifying the log level and filter criteria for a log category