Urgent. How to trace Rest service call on Pega

Hi all,

We are seeing some issues with our Rest services on production. We have pooling for the service package set as 10 - Active users,10 - Idle,10 - wait time. We don't have dev portal access on production and so we can't login to one node and trace the service rule. On SMA , as Pega creates a service requestor on the go, we can't select a requestor and trace.

Is there any way to trace the service call without dev portal access?

***Edited by Moderator Marissa to update platform capability tags****


Keep up to date on this post and subscribe to comments

September 19, 2019 - 9:26pm

You can try to enable the debug log:

September 28, 2019 - 10:26pm
Response to KevinZheng_GCS

Hi Kevin,

   Thank you for your prompt response. I will try this logger and get back to you.



September 20, 2019 - 12:18am


Please let us know exact pega version, based on that loggers may change.

You can try : 


September 28, 2019 - 10:26pm
Response to agarp3

Hi agar,

  We are using pega 7.4 version. I will try with these loggers and get back to you. Thank you for your prompt response.

September 29, 2019 - 3:25am

Hi Durga,

Are you getting any exception in pegarules logs.Please search for "timeout borrowing requestor" exception & let me know.



October 17, 2019 - 8:40pm
Response to Abhinav7

Hi Rahul,  Yes we are receiving Time out exception error in the log messages. Currently we are daily monitoring the nodes for any timeouts after increasing the requestor pool to 40. 

October 18, 2019 - 2:05am
Response to DurgaPrasadBali

Hi Durga,

Fine, Is your application stable after increasing it?