Hello, I have a situation in my application where PEGA005 alerts are triggered for a query which is called from Connect-SQL rule. We use Stored Proc to pull the data from DB tables considering the complexity. We have configured our Connect-SQL rule to trigger the Stored Proc and we pass the values as page reference using "ASIS:" keyword. Sometimes the where clause would include sensitive information which is not supposed to be exposed.

As PEGA005 DB alerts are triggered when the threshold limit exceeds, PEGA writes the SQL content along with the ASIS references passed to Alert logs which exposes the sensitive information.

How do I suppress the ASIS values not to be written to the Alert logs?

I have referred many articles in PDN, but I do not see any questions on this scenario.

For regular sql queries which are triggered either by Connect-SQL, RD or Obj methods, we have updated the suppressInserts variable to "true" in prconfig and it works good.

https://docs.pega.com/bundle/alerts/page/platform/alerts/pega0005-alert-query-time-exceeds-limit.html

I'm looking similar configuration when Stored Procs are used. 

Thanks in Advance!