How to detect large HTML streams (PEGA0029 alert)

Alert log message

When an HTML stream is sent to a browser and the number of bytes exceeds a threshold value, a PEGA0029 alert message appears in the alert log. Here is an example:

Stream exceeded client response byte threshold (pxObjClass=Rule-Obj-HTML;pyStreamName=Web-Login;).

Other fields in the alert log message identify the pzInsKey or the rule class of the stream and its keys.

Modifying the alert settings

By default, the alert is enabled with a threshold of 204,800 bytes (2000 KB). This alert is not triggered by streams generated in a Developer portal (authenticated users who can check out rules). You can modify the settings in the prconfig.xml file as follows:

1. Open the prconfig.xml file and update this alerts section:

<env name="alerts/clientbytesreturned/enabled" value="true" />
<env name="alerts/clientbytesreturned/threshold"
      value="204800" />
<env name="alerts/clientbytesreturned/ignoredevusers" value="true" />

2. Set the desired threshold value using a positive integer identifying the size in bytes.
3. Set the enabled value to false to disable the alert. The default is true.
4. Set the ignoredevusers value to false to include streams produced by developers. The default is true.
5. Stop and restart the server.

Probable causes and remediation

Here are likely reasons for the alert and suggestions on how to address them:

• A screen contains too much content. Consider moving content into separate screens. Also consider moving non-dynamic elements such as style sheets and scripting into static content using a Rule-File-Text rule type. This reduces browser traffic and takes advantage of client-side caching mechanisms.
• A screen contains large lists. If possible, implement a paging mechanism for the list.

PDN Resource

For an example, see Pega Developer Network article PRKB-25619 Understanding the PEGA0029 alert.

	alert log, prconfig.xml file, stream processing
	Understanding alerts

SysAdmin category