Pega0069 Alerts in relation to other Pega Alerts
Performance Tool (PAL) numbers for Pega0069 Alerts such as pxConnectElapsed are above threshold but no corresponding Pega0020 Alert can be found.
This is observed with some other PAL values such as pxOtherIOElapsed and pxRDBIOElapsed as well.
Steps to Reproduce
Refer to the product documentation: https://pdn.pega.com/pega0069-alert-client-page-load-time/pega0069-alert-client-page-load-time This PDN link has brief explanation for Pega0069 Alert.
Here’s the explanation for the reported behavior:
Pega0069 Alerts may be generated from multiple server interactions and its PAL counters are cumulative values.
These numbers for pxConnectElapsed may seem high enough (> 1000ms for Pega0020) to warrant a separate Alert, but might not always see those if there are multiple server interactions.
These server interactions may be Connector calls or DB calls (in case of pxRDBIOElapsed related Pega0005 alert) and the individual server interaction time might not be above the threshold.
Also keep in mind that pxConnectCount and pxRDBIOCount values in such cases will also have an impact on the time spent on a single Connect or RDBIO interaction.