Hi Nagarjuna,

Thanks for posting on PSC.

Add the following setting to prconfig.xml to suppress the sensitive property values:
<env name="alerts/database/operationTimeThreshold/suppressInserts" value="true" />
This setting will suppress the sensitive property values (and replace them with question marks).

To suppress information in parameters, add the following setting to prconfig.xml:
<env name="alerts/general/includeparameterpage" value="false" />
This setting determines if the parameter page of the top-most stackframe will be included in the ALERT log when the alert is generated.

Re-start the server after changes made.

Try using configuration. Hope it helps. Kindly notify, if it does.

Regards,

Asif

Did you try with the Default value allowed

the DSS prconfig/alerts/parameterpage/remoteFilterType/default should be set to "obfuscate". The default value is "allowed"

Ref: https://pdn.pega.com/community/pega-product-support/question/can-parameterpage-values-be-supressed-pega0001-alert-log​

Hello Nagarjuna,

The following prconfig entry will do obfuscation of parameter values 

<envname="alerts/parameterpage/remoteFilterType" value="obfuscate" />.

You can specify the parameters to obfuscate in the alert logs using 

<envname="alerts/parameterpage/obfuscateKeywords" value="" />

,The value should contain the parameter names separated by semi-colon.

Thanks,

Arun

I forgot to mention you missed  below entry in the prconfig/DSS to obfuscate the parameters in alert logs.

<envname="alerts/parameterpage/obfuscateKeywords" value="" />

Thanks,

Arun

In the 8.1 the white list using allowed keywords of the parameter page will be the default for both the file system and PDC/AES. This will resolve the security issue of data in the filesystem for alerts. There are also hotfixes available to make white list the only option for the filesystem.