ClientPageLoad Alert (Pega0069), Slow rendering in browser
As per pega documentation for Pega0069, the alert should be showing up "load duration" which helps in debugging if the issue is on server, client or network.
https://docs-previous.pega.com/pega0069-alert-client-page-load-time
At our side, we don't see the "load duration" for any of the Pega0069 alert. Any configuration issue ?
Pegasystems Inc.
GB
@FnuA8586 as per the discussion in a previous forum post, there may be a slight discrepancy between the format shown in the documentation and the one generated by your system.
Pega0069 alerts if shown as top offender, indicates, there are performance issues.
You should review your Pega logs, Pega alert to see if there is an odd event, thread dump etc. Review PDC to see what is causing performance issue.
If your alert log contains a large number of PEGA0069 messages, a problem on the server, network, or client might be causing screens to take a long time to load. Using the message text, compare the load duration to the server duration to narrow down the issue to the server, client, or network. The action specified in the alert message can also help you determine which screen or action caused the alert.
Other alerts that are triggered by this screen load have the same requestor ID and page load counter as the PEGA0069 alert. You can use this information to correlate those alerts to the PEGA0069 alert.It will be dependent on some other alert.
I will check internally to see if the documentation needs to be updated in any way.
@FnuA8586 as per the discussion in a previous forum post, there may be a slight discrepancy between the format shown in the documentation and the one generated by your system.
Pega0069 alerts if shown as top offender, indicates, there are performance issues.
You should review your Pega logs, Pega alert to see if there is an odd event, thread dump etc. Review PDC to see what is causing performance issue.
If your alert log contains a large number of PEGA0069 messages, a problem on the server, network, or client might be causing screens to take a long time to load. Using the message text, compare the load duration to the server duration to narrow down the issue to the server, client, or network. The action specified in the alert message can also help you determine which screen or action caused the alert.
Other alerts that are triggered by this screen load have the same requestor ID and page load counter as the PEGA0069 alert. You can use this information to correlate those alerts to the PEGA0069 alert.It will be dependent on some other alert.
I will check internally to see if the documentation needs to be updated in any way.
If you require an in-depth analysis of your issue, please could you log a support incident and let us know the INC number so that we can help track it?
State of New Jersey
US
thank you Marije for your update !
1. PDC is not helpful for this scenario(may be) attached screenshot for reference , as the correlated event for that requestor took very less time. Also very less GC time. Any insight or thought if you have for where the extra time is coming from ?
2. Usually pxClientLoadElapsed(Pega0069) alert will add up to the total Elapsed time , in attached screenshots it is not adding. not sure what contributed that extra time. Any insight or thought if you have for where the extra time is coming from ?
Pegasystems Inc.
GB
@FnuA8586 I have asked an SME to comment on possible reasons why that information may be missing, but if you need an in-depth analysis of your particular example I would suggest that you log a support incident for this so that our team can look into all the details in the logs leading to the alert.
If you decide to log a ticket, could you provide the INC number here so that we can help track it?
State of New Jersey
US
thanks Marije ! if you get update from the SME please share and for the ticket if I raise , will update the post.