Skip to main content


         This documentation site is for previous versions. Visit our new documentation site for current releases.      
 

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.

Suppressing sensitive data in alerts

Updated on April 5, 2022

The alert log identifies the names of activities and other rules that have been executed. By default, PEGA0002 to PEGA0007 alerts also show parameter values and SQL statements containing property values. You can include the suppressInserts and includeParameterPage keywords in the prconfig.xml file so that parameter values and other potentially sensitive data values are omitted in prepared statement inserts:

For a complete list of alert log settings, refer to the Pega Community article Security settings in the prconfig.xml file.
  1. Add the following to the prconfig.xml file:

    <env name="alerts/database/operationTimeThreshold/suppressInserts"
    value="true" />
    <env name="alerts/general/includeParameterPage" value="false" />
  2. Stop and restart or redeploy the system.

Have a question? Get answers now.

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

Did you find this content helpful?

Want to help us improve this content?

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