Tracing whole session leads to stuck my system even though i have marked only required ruleset, What is the solution for this? Also please help me to understand how to trace individual rules (DT, Activity ) only from the entire session, Thank You…
The safer approach is to use session tracing only when necessary and narrow the trace to the specific rule type or page you are investigating. Use Tracer from Dev Studio only for the relevant request and not for long-running session-wide tracing. Full session trace is supported, but it is also the most expensive option.
For Constellation, enable the View Rules option in the tracer when you need to inspect view metadata and rendering behaviour. If you are debugging a specific API-driven interaction, trace the Service REST rule instead of the whole UI session
For individual rules such as Activity or Data Transform, open the rule directly in Dev Studio, run it in a controlled context from a harness or test case or rule execution path that invokes only that rule and turn on tracing for that run so you can see just the rule execution chain you care about.
Pega does not really give you a “trace only one rule in isolation” switch for an arbitrary live session. You trace the execution path, then narrow it by calling only the rule you want to inspect.
You can trace individual rules instead of the entire session by configuring filters in Tracer. Open Tracer, go to Settings, and select only the required event types such as Decision Table and Activity. Then apply appropriate ruleset, rule type, or rule name filters to limit the trace output to the specific rules you want to analyze. This helps reduce the amount of trace data generated, improves performance, and makes it easier to identify the execution flow of the targeted rules without tracing the entire session.
Click Settings.
In the Tracer settings you will find these popup and you can trace a specific rule if you want to trace DT then check the Box of DT only the DT rules only you will see
