PEGA0005 alert: Query time exceeds limit
The PEGA0005 alert is triggered when the elapsed time for a query to the PegaRULES database exceeds the operation time threshold setting. Using the threshold setting helps you recognize when queries are inefficiently designed and when data is being loaded indiscriminately.
Example message text
Database query took more than threshold of 500 ms: 4771.24 ms SQL: select pzInsKey, pyRuleStarts, pyRuleSet, pyRuleSetVersion, pyClassName, pyRuleAvailable, pyRuleEnds, pyCircumstanceProp, pyCircumstanceVal, pyCircumstanceDateProp, pyCircumstanceDate from pr4_rule where pxObjClass = ? and pxInsId = ?
suppressInsertssetting, which prevents sensitive property values from being output to the Alert log. Depending on who is viewing the data, this setting might be important, because some of the data being sent might include system or database passwords (if they are not encrypted).
Default prconfig.xml settings
<env name="alerts/database/operationTimeThreshold" value="500" />
The default threshold is 500 milliseconds (1/2 second).
<env name="alerts/database/operationTimeThreshold/suppressInserts" value="true" />
Toggles the trigger for suppressing insert operations on ("true") or off ("false"). See the note above.
Reasons for the alert
Examine the text of the alert message that describes the SQL statement that the system was trying to execute. Ask your database administrator to analyze the SQL to determine whether there are problems with the information that is being requested from the database (for example, is the system trying to query information from the BLOB).