How to get request hitting time at pega for an exposed SOAP Service


We are troubleshooting an issue occurred in production where we exposed SOAP service in Pega and is being invoked by other applications, some how request is sent to pega from other system and response received at other system from pega after 2 mins. which made timeout and caused data issues.

is there a way in pega that we can identify the time that pega receives request?


Keep up to date on this post and subscribe to comments

August 22, 2019 - 1:01pm


Please find below document link and refer the section 'Performance Statistics for Services Running'. 

Additionally, if you're using any external tools viz AppDynamics, Fiddler then you may get the network trace details. You may also check the PegaALERT logs while invoking the webservice if any alert among PEGA0011, PEGA0012, PEGA0013, PEGA0014 and PEGA0015 get logged. Hope it will help you.


August 22, 2019 - 5:50pm

1. Change the logging level of class to Debug, and it would start writing logs as soon as a new request hits your service.

2. Save as your service activity in production ruleset to add a log-message step at the beginning. Log the current date time at that step.

August 22, 2019 - 8:27pm
Response to N.SenSharma

We are troubleshooting the issue occurred in production, it wont help putting the debug at the log level or make changes in activity. we are trying to find the way how we can find the time of service request already hit the system.

August 23, 2019 - 10:12am

Putting debug at the log level wont help for the services which were already processed. Could you please check if there is any alert in the PegaAlert log for the same time when we got the request and the response was sent.

Thank You,

September 6, 2019 - 12:41am
Response to dasn1

Hi, There is no alert reported in the PegaAlert log.

September 7, 2019 - 12:08am

Hi Mohammad,

Could you add your own

property-set or Log-Message step @(Pega-RULES:DateTime).CurrentDateTime() to capture the time?