Pega Platform maintains statistics about the number of rule executions since startup. During system shutdown, the system saves these statistics to the Pega Platform database for later review and analysis.
The system holds these statistics as property values in the Log-RuleUsage class, with additional detail in the Log-RuleUsage-Details class.
How it works
Pega Platform maintains statistics during operation which are written to the Pega Platform database for later review and analysis during application server shutdown.
These statistics cover all requestors of every type, with cumulative statistics since startup. This can be helpful in identifying the most frequently and least frequently executed rules (for those rule types that are assembled using rules assembly).
By "rule," this topic means "a Java class created by rules assembly." One Pega Platform activity named Alpha-Mort-.Recalculate might produce multiple rules, one for each variation in:
- Primary page class at the time of assembly (for subclasses of Alpha-Mort-.)
- Ruleset and version
- Ruleset list of the requestor
The value of the
key property of a
is concatenated from these other property values:
- pxClassName – Always
- pxSystemNode – Node ID of the node from which the snapshot was captured
- The full Java class name of the assembled rule, starting with a type.
- pyLabel – The snapshot name, such as "shutdown"
The Java class name identifies the rule type. Three examples are:
Unlike most other concrete classes derived from the Log- base class, the pxCreateDateTime property is not part of the key of the Log-RuleUsage class.
Statistics in Log-RuleUsage
The following properties are of primary interest in each snapshot row. All statistics are since startup of a node or since installation, covering all requestors of all types.
|Identifies the type of snapshot. The value "shutdown" is reserved.
|Full Java class name for the rule-assembled rule.
| Rule type concatenated with visible key, converted to lowercase characters and
converting special characters to underscore characters. For example:
|Date and time that the rule was last executed.
|Number of times the class loader checked to see whether this entry was loaded.
|Number of times the cache content was invalidated (unloaded), such that the next request forces rules assembly.
|Number of times this class was loaded.
|Number of times this class was reloaded without forcing a rules assembly.
|Number of dependences that this rule has.
|First date and time this rule was captured by this snapshot.
|Most recent date and time this rule was captured by this snapshot.
|Size of the Java CLASS file in bytes.
|Node ID (hash) on which this snapshot was captured.
|Number of times this rule was requested from the cache.
No automatic processing purges rows of the
pr4_log_usage table. If your
system has been shut down more than once, statistics for pxNumInvalidate,
pxNumLoads are cumulative since installation. Statistics for
pxUpdateDateTime, pxLastUse are from the most recent