Question

5
Replies
1017
Views
Posted: 4 years agoUpdated: 4 years ago
Closed
Solved

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

This thread is closed to future replies. Content and links will no longer be updated. If you have the same/similar Question, please write a new Question.
Accepted Solution
Posted: 4 years ago

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.
Posted: 4 years ago

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.
Posted: 4 years ago

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
Posted: 4 years ago

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.