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.

Reporting on rule usage snapshots

Updated on April 5, 2022

Pega Platform maintains statistics about the number of rule executions since startup. Create and view reports about these shutdown statistics to understand which rules execute most often, and which execute rarely or not at all. Viewing these statistics can help you identify the causes of variations in system performance.

The system holds these statistics as property values in the Log-RuleUsage class, with additional detail in the Log-RuleUsage-Details class. In the normal table mapping, the system saves these statistics a row of the pr4_log_usage and pr4_log_rule_usage tables. For a description of the properties in these classes, see Rule usage snapshots.

Choose from the following, depending on your needs and system access.

  • Create a report on the Log-RuleUsage or the Log-RuleUsage-Details class.
    You can filter the report on any exposed property such as node ID, snapshot name, update timestamp, and so forth.
  • In Dev Studio, in the navigation pane, click App, and then do the following steps.
    1. In the class name field, enter Log-RuleUsage.
    2. To see a list of instances, click the Log-RuleUsage label.
    3. To see the property values for an instance in clipboard format, click on an instance.
  • If you have direct database access, use SQL tools to view and filter the contents of the pr4_log_usage and pr4_log_rule_usage tables.

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