Skip to main content


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

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.

Selecting a session to trace

Updated on April 5, 2022

By default, the Tracer traces your own requestor session. You can trace another session by using the Remote Tracer. The Remote Tracer lists every requestor that is connected to your Pega Platform server.

The first letter of the session ID identifies the requestor type:

  • H – Internet Explorer-based users
  • B – Background users such as agents, service requestors other than for Service Portal rules, and daemons
  • A – External applications
  • P – Access through Service Portlet rules

You cannot trace listener processing because listeners operate as Java threads, not full requestor sessions. Use remote logging to debug listeners.

  1. On the developer toolbar, click Tracer, or click ActionsTrace on an activity, data transform, or service rule form.
  2. Click Remote Tracer.
  3. Select the session that you want to trace.
  4. Click Okay.

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.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us