Where API Connector Errors are captured in Pega, OOTB way? What is the table that stores the data?

General
, , , ,
1

There is a requirement to get the historical data of All the External API’s Pega connectors for the last quarter to check how many of them got Timeout or other errors.

We are not getting any place to see where Pega writes this information OOTB way, if errors are not handled in explicit custom way.

I checked the .pyErrorPage which generates in runtime and under the Primary page of Invoke activity, usually gets saved in Embed-Error, which mapped to table data.pr_other in PegaDATA, did not find anything over there.

Also checked Log-Connect-Error class which has an activity called ‘Add’, it seems this logs the records when errors in runtime, but did not get any reference from activities like - Invoke, pyInvokeRequestor etc. or from Pega-IntSvcs agents like ProcessConnectQueue etc.

So, requesting your ideas here if any.

2

@RanadipD0478 - Pega doesn’t store the errors happening in connectors. You can have your own class to store this if needed and you can have an activity which can be invoked from connector’s Invoke activities to do so.

Another approach is to identify it from logs. Ideally exception for any connector should be logged in the PegaRULES.log file. If you are using Pega cloud you can ask for Kibana access using which you can setup a dashboard to view the above exceptions.

3

@KALINGAROUT thanks for the confirmation, I have the same idea about it, but wanted to be double sure.