Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

Remote tracer results contain rulesets that were not selected



Developer complaints that when they are trying to do remote tracing and selecting specific ruleset from tracer settings, the selected ruleset setting is not getting respected instead all the ruleset rules are getting traced.

Error Messages

Not Applicable

Steps to Reproduce

1. Open tracer.
2. Click Remote tracer.
3. Choose requestor.
4. Open Settings.
5. Chose ruleset.
6. Trace.
7. See that results contain unnecessary rows.

Root Cause

This issue was determined to be a product enhancement request. As per user expectation, user wants to see the remote tracer results with the rulesets which are selected. 
However, this is not possible as per current functionality. when performing a remote trace, the system does not take into account the settings on the ruleset list as we are tracing a different requestor. The other target requestor we are trying to trace could have a completely different ruleset stack.
Hence, PRPC will trace all rulesets of the target or remote requestor.


An enhancement request, FDBK-15186, has been created for consideration by Pega Product Management. 

Published May 14, 2016 - Updated October 8, 2020

Was this useful?

0% found this useful

Have a question? Get answers now.

Visit the Collaboration 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.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us