Executive Summary  

Pega Cloud has identified performance issues related to the increasing size of the pr_data_svcinvhist table following the enablement of Service monitoring in production. 

Pega Cloud recommends that clients implement the proactive measures outlined below to ensure ongoing table maintenance and hygiene.  

Analysis and Root Cause: 

The root cause has been identified as the agent responsible for purging records not functioning properly. This happens as the underlying DB query times out. 

Proactive steps to be performed: 

• Review your service monitoring configurations. Where the pr_data_svcinvhist table has increased in size, you should raise a Cloud Change (CC) case requesting table truncation. Pega Support will work with you to complete this task. Review Configure Service rest rule monitoring  for details. 

  • If monitoring is enabled, ensure it is disabled, as it is not recommended for production environments.  If you need to maintain monitoring for debugging purposes, you can use the OOTB log category <pxIntegration.Service.Rest>, which will capture both request and response payloads in the logs. 
  • If you are dealing with intermittent issues and wish to keep monitoring enabled, consider updating the DSS service/EnableGlobalMonitoring to Deferred and configure it at the Service package or rest rule level.  

• Additionally, to ensure automatic purging of invocation history, enable the agent pzCleanupServiceMonitorInstances and make sure to set the periodic interval to no less than 10 minutes. More details on this can be found at:  Automatically purging invocation history 

If you have any questions or concerns, please raise a Support ticket with Global Client Support in My Support Portal for assistance.