Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

Pega0069 Alerts in relation to other Pega Alerts

SA-39643

Summary



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.


Error Messages



Not Applicable


Steps to Reproduce



Not Applicable


Root Cause



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.

Resolution



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.

Suggest Edit

Published August 21, 2017 - Updated October 8, 2020

Did you find this content helpful? Yes No

100% found this useful

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us