Skip to main content


         This documentation site is for previous versions. Visit our new documentation site for current releases.      
 

This content has been archived and is no longer being updated.

Links may not function; however, this content may be relevant to outdated versions of the product.

Managing log categories

Updated on April 5, 2022

From Admin Studio, you can select which log messages to write to your log files by associating log levels with your categories.

The log level of a category determines which messages are written to the log file. When you create a log category and set its default log level, these selections apply to all nodes in the cluster and they persist until you change them. The default log level applies to all the loggers that you associate with your category.

To view log categories, you must have the pzLogLevelObserver privilege, and to edit log categories, you must have the pzLogLevelAdministrator privilege.

  • Changing log levels for custom log categories

    Change the number of log messages that are written to the log file by changing the log level of your custom log categories. For example, if the default log level for your category is OFF, no log messages are written to the log file. To include severe errors in the log file, set the log level to FATAL.

  • Log levels for log categories

    You can select which log messages your log files include by creating log categories and associating log levels with your categories.

  • Restoring log level default values

    You can restore the default log levels of all your custom categories at once by resetting their log levels.

  • Setting log levels for individual loggers

    When you create a log category, all the loggers that you associate with this category have the same log level. You can assign a different log level to individual loggers.

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us