Skip to main content

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

Tracer results window

Updated on August 25, 2021

The header row of the tracer results window contains the Pega node hash and computer name. For cluster-wide tracing of service rules, the tracer displays a separate section for each node that reported events.

The tracer records selected events from the rule executions, database operations, and other event types that you selected when you configured the Tracer. Each row represents an event and is color-coded.

  • Gray – Activity processing
  • Orange – Events from flow, decision, or declarative rules
  • Light blue – PegaRULES database and cache operations

The window contains the following columns. The values of some columns change depending on the type of traced event.

LineNumber of events traced, starting at 1 for the oldest.
Thread The Thread object for the step.
IntThe interaction number for the step. This total starts being counted at login and is reset upon logout.
Rule# Count of distinct activities traced. The count is not reset to zero if you clear all the events. When a single activity is run again later, the previously assigned number is repeated.

Rules other than activities are not assigned a number.

Step Method For an activity, the method in this step.

For a declarative rule or decision rule, indicates the start or end of a computation.

For a when condition rule or Boolean expression, identifies the rule name or (a portion of) the expression.

When you trace a database operation , this column lists the specific operation performed on the database. (commit, insert, update)

Step Page Name of the step page, or =unnamed= if the Step Page column of this step is blank. Step pages that have messages set on them, such as error messages, have a bright orange background.

When you trace a database operation , this column lists the database table affected by the database operation in the Step Method column.

StepStep number of this step. If two or more rows appear with the same step number, an iteration is in process at that step.
Status Status of the method in the step, from the pxMethodStatus property, such as Good, Fail, or Warn. A red background marks Fail steps (that are not addressed by a transition).

Exit Iteration marks the end of an iteration step.

In this context, a red Fail row indicates an unhandled exception condition. If a method returns a Fail status but the step contains a transition, the Tracer row displays the status as Good and has a normal gray background. This behavior is consistent with the processing status that is to be perceived by the next activity step to run; it reflects that any error condition that existed has been noted by the activity.

When you trace a database operation , this column lists the number of bytes involved in a write to the database.

WatchProperties for which you have set up a watch variable.
Event Type Type of event or rule: Step Begin, Step End, Activity End, Constraint, Expression, DecisionTree, MapValue, and so on. When Begin and When End events identify the start of a when condition rule or similar test, such as in a precondition or transition.
Elapsed For Step End and Activity End rows, elapsed time in seconds for the step. The time interval might be degraded by Tracer operation.
Name Full name of the rule being traced, showing all key parts.

When you trace a database or cache operation , the Name and RuleSet columns are combined. The text in this combined column provides details on the rules being searched for in the cache, or on the size of the database operation.

RulesetRuleset and version containing the rule being traced.
  • Previous topic Viewing system settings in on-premise systems for troubleshooting
  • Next topic Troubleshooting background processing

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