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.

Understanding alert message settings in the prconfig.xml file

Suggest edit
Updated on April 5, 2022

There are three optional settings in the prconfig.xml file that affect how alert messages are generated. You can modify the default values by editing the settings in the prconfig.xml file.

For information about editing these settings, see How to change prconfig.xml file settings.

General alert prconfig.xml settings

Use the following prconfig.xml settings to control overall alert logging behavior:

includeSQLInTraceList

<env name="alerts/database/includeSQLInTraceList" value="false" />

Adds the executed SQL to the trace list displayed in certain alerts.

includeparameterpage

<env name="alerts/general/includeparameterpage" value="true" />

Adds the parameter page data to the alerts

stackdepth

<env name=" alerts/general/stackdepth" value="5" />

Sets the depth of the stack to display in the alerts.

If these settings are not included in the prconfig.xml file or Dynamic System Settings, the default behavior is as shown above.

Additional alert prconfig.xml settings

Many alerts have related threshold settings in the prconfig.xml file that define a value that, when exceeded, trigger an alert. For example, number of bytes or rows. You can also toggle some alerts on or off using the enabledsetting.

Did you find this content helpful? YesNo

Have a question? Get answers now.

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

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

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us