PEGA0069 alert: Client page load time

The PEGA0069 alert is generated when the total elapsed time from when the user clicks to when the screen has finished being rendered exceeds the configured threshold (in milliseconds). Unlike other alerts, this alert can include more than one server interaction; therefore, Performance Analyzer (PAL) data is a cumulative counter for all server interactions.

Example message text – one server interaction

ClientPageLoad has exceeded the elapsed time alert threshold of 100 ms, load duration 2025 ms, server duration 99 ms, server interactions 1, action:openWorkByHandle|key:AAA-APPPA-WORK C-1|.

Example message text – multiple server interactions

ClientPageLoad has exceeded the elapsed time alert threshold of 4000 ms, load duration 10048 ms, server duration 7043 ms, server interactions 7, load description action:openWorkByHandle|key:AAA-APPPA-WORK C-1|.*

Dynamic System Setting

You can override the default setting of 4000 ms on all nodes in a cluster by adding the following Dynamic System Setting. Changing the prconfix.xml file only changes the node on which the file resides.

After you change the setting, restart all nodes for the changes to take effect.

Owning ruleset: Pega-Engine

Setting purpose: alerts/browser/clientPageLoadTimeThreshold/warnMS

Value: <threshold in milliseconds>

Default prconfig.xml setting

warnMS (where "MS" is milliseconds)

<env name="alerts/browser/clientPageLoadTimeThreshold/warnMS" value="4000" />

The threshold value in milliseconds. The default value is 4000 milliseconds.

Probable reasons for alert

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.

Suggest Edit

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.