How the invocation of services works in pega?
I want to capture the invocation (start and finish) of services ( Service REST, Service SOAP, etc.) in Pega so that I can log specific data in my custom log file like the start time of the invocation when the invocation is finished and certain other data ( like request, response, HTTP status, etc.). I tried to find multiple documentation on the Pega community but there was no solution or details available. I have checked that Pega captures the service invocation history in the service package. How does it captures the invocation history and if I want to capture the same but with my custom set of data then how can I do that?
Capgemini
IN
Could you please try to enable debug logging below classes ..go to system->operations ->logs->logging level settings
change the current level to debug or info to get the payload and request/response after entering the below loggers under the logger name
com.pega.pegarules.integration.engine.internal.services.RESTServiceAPI com.pega.pegarules.integration.engine.internal.services.soap.SOAPService com.pega.pegarules.integration.engine.internal.ServiceMappingUtils
Knowledge Expert
NL
Hi @Bharath.Suntigikar, Thanks for the quick response. I checked that all the 3 loggers are already present but with an ERROR logging level. Actually, my requirement is to find the function ( Activity, DT, Java code, etc.) from where Pega invokes the action to capture these data. For example, for Connect REST, Pega always executes the "pyInvokeRESTConnector" activity, so I can override this activity to add my data to pass it in the log before and after calling the integration ( As in the screenshot).
I need to find something similar for Service REST to track when the integration started and when it finished and what data came as input and what went to output, etc.
Updated: 11 Jul 2022 9:39 EDT
Capgemini
IN
- In the navigation panel, click Records-Integration-Resources-Service Package.
- Click the service package that contains the rule for which you want to view results.
- Click view in the Invocation history column for the service that you want to view.
- The Service request invocation history dialog box displays information about each invocation of the Service REST rule, including when the request was received, the IP address, status, the elapsed time on the server side (not including latency), request and response payload, the number of attachments, and the node Id. You can perform the following actions:
(i)To view the request and response results, and if configured, the clipboard state, in the Invocation Id column, click the invocation Id. By default, a maximum of 3000 characters are displayed for the request and response data. To change the number of characters, in the Showing field, enter the number of characters that you want to view and click Apply. Click the Clipboard tab to view the state of clipboard's primary page.
- In the navigation panel, click Records-Integration-Resources-Service Package.
- Click the service package that contains the rule for which you want to view results.
- Click view in the Invocation history column for the service that you want to view.
- The Service request invocation history dialog box displays information about each invocation of the Service REST rule, including when the request was received, the IP address, status, the elapsed time on the server side (not including latency), request and response payload, the number of attachments, and the node Id. You can perform the following actions:
(i)To view the request and response results, and if configured, the clipboard state, in the Invocation Id column, click the invocation Id. By default, a maximum of 3000 characters are displayed for the request and response data. To change the number of characters, in the Showing field, enter the number of characters that you want to view and click Apply. Click the Clipboard tab to view the state of clipboard's primary page.
(ii) To view a list of attachments by request and response, in the Attachments field, click the number of attachments.
note:
you can view the monitoring results on the service package rule in the invocation history section. From the invocation history, you can click a particular invocation to view the actual request, response, and if configured, the clipboard state at the time the rule was invoked. You must have the prDeveloperForm privilege to view invocation history.
Knowledge Expert
NL
Hi @Bharath.Suntigikar , as I have mentioned in my actual description of the question, I already know about checking the data from the Service Package invocation history but I am trying to find that how that data is added there, which function, Activity, DT, etc. in Pega is responsible for that?
If I want to add the same data to my custom log how will it be possible? That's why I am looking for the Pega inbuilt function which adds the data in the Invocation History of Service Package so that I can modify that function and capture the data in my custom log.