Need to log Failure request and response of PEGA OOTB Cases API

General
1

We need to login Failure Request and Response into our custom table to track Cases API Failures caused by external teams

2

You can view the monitoring results on the service package rule in the invocation history section. From there, you can click a particular invocation and view the actual request, response, and if configured, the clipboard state at the time the rule was invoked. However, it’s not recommended to enable it on Production. This could slow down the performance in Production.

Please find the link for more details - Pegasystems Documentation

3

  1. How can I log in Production with out impacting performance ? Is there any way to measure performance of application once we checked it

  2. Which OOTB table these Invocation History will be saved ?

  3. How frequent these invocation history logs will be cleared ? If we need to cleanup which table we need to cleanup ?

4

  1. Please be mindful to capture the request and response because it can contain PII data. If you’re looking to troubleshoot issues, then enable the logs for a short period of time.

  2. pr_data_svclog

  3. Pegasystems Documentation

5

You can have a separate class and save request and response as blob instances to this class.

6

1) Preference for Out-of-the-Box Solutions: Please advise out-of-the-box features for logging solution that enables the required logging (ONLY Failure Logging) without customization of OOTB Cases API.

2) API Pod Logging Isolation: We have separate API pods and we can do logging on API pods, which are separate from user pods, to ensure isolation and minimize performance impact, and could you suggest if there are any config values which can be added to API pods to enhance current logging