Skip to main content

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

Modifying the log level and filter criteria for a log category

Updated on July 8, 2022

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.

Before you begin: Operations on log categories require the following privileges:
  • pzLogLevelObserver to view log categories.
  • pzLogLevelAdministrator to edit log categories.
  1. In the navigation pane of Admin Studio, click ResourcesLog categories.
  2. For the log category that you want to modify, click the More icon and then click Change log level.
  3. In the Log level list, select the log level that you want to apply to the log category.
  4. To increase the time until Pega Platform resets the log level and filter criteria back to their default settings, select a different Reset period.
  5. If you change the log level to ERROR or Debug, then you can filter events in the log file for specific operators, rule types, classes, or rules:
    • To filter logging events based on a specific user, in the Operator field, enter the operator ID.
    • To filter logging events based on a specific type of rule, in the Rule Type list, select the type of rule. You can filter events for an activity, data transform, automation, REST service, or queue processor rule type. If you are filtering based on an activity, data transform, or automation rule, then select the class for the rule.
    • To filter logging events based on a specific rule, in the Rule field, enter the rule that you want to include in the log results.
  6. Click Submit.

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. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us