Posted: 19 Oct 2015 14:51 EDT Last activity: 6 Apr 2018 19:26 EDT
How to capture total processing time in Pega for a request that comes in Pega application by Service SOAP
Problem Statement :
In our claims Pega application there are multiple surrounding systems which are acessing information stored at pega databse via calling Soap service. We have exposed one Service SOAP from Pega and all other systems are comsuming the same. The current issue that we are facing during open enrollment period multiple slowness issues have been reported from surrounding systems, but no one is able to identify where the actual slowness is occuring.
Therefore client want us to capture the total processing time in Pega starting from the request rceive in Pega till the response goes out from Pega.
Approach : To address this issue we are looking for what is the best possible approach to capture end to end processing time in Pega. Is there a configuration that we can enable to capture this in Log, or what will be the best possible place ( e.g. Service activity) to put some code to capture time.
**Moderation Team has archived post**
This post has been archived for educational purposes. Contents and links will no longer be updated. If you have the same/similar question, please write a new post.
Not sure about the best possible way. One approach can be, on the first step of the service activity, read the current time and have in a property. And in the last step of the Service acivity read the current time and calculate the difference between start timestamp, that gives the total time taken to complete the Service activity.
@Vignesh: Alerts are generated in ALERT log only when interaction time exceeds the threshold time defined in prconfig.xml and cannot track time consumed in serving each request. Moreover it cannot be reported.
The best approach would be creating a dedicated DB table with "Time Difference" as one of the column and other columns as necessary.
By analyzing the patterns from the reports generated on this class, the cause of the issue may be derived.
Certainly the code needs to be modified but maintenance becomes lot easier.
Posted: 5 years ago
Updated: 5 years ago
Posted: 21 Mar 2016 4:59 EDT Updated: 21 Mar 2016 5:02 EDT