Question
Remote Tracer traces extra rule.
When we do Remote trace for a particular user.
Tracer Setting: Tracer only my application ruleset.
But the tracer traces all the pega rule instead of just my application ruleset.
How to fix this, any idea?
P.S
I am using Pega 7.1.7
okay, Is there a way to handle this, last time I handled it using private checkout pega rules, Is there any other way.
It becomes little harder to debug when 1000 of lines of pega code are getting traced which you are not bothered for.
Well I am not aware of something like that. One alternate option could be to save the tracer dump first ( in *.xml format ) in your local system and then use tracer viewer tool to upload the same and filter it / find the rules accordingly.
Details for the tracer viewer tool is here : https://pdn.pega.com/use-tracer-viewer-tool-summarize-tracer-xml-output
Would it be useful to filter in either of the following ways ?
- Unselect "activity steps" so you only see the activity entrances and exits. This makes the tracer much shorter
- Trace a specific activity instead of everything. (I'm not sure you can do this with remote tracing)
/Eric
Eric your suggestion seems good and was useful in some cases.
But sometime we need the entire trace of the application specific rule.
The View tracer tool seems useful one.
Can filter out the pega rule, but can minimize them in the tree structure.
When performing a remote trace, the system does not take into account your settings on the ruleset list because you are tracing a different requestor. The other target requestor you are trying to trace could have a completely different ruleset stack. Hence, PRPC will trace all rulesets of the target/remote requestor.