In my project one of the activity causing an DB alert and which retrieves all DB records as part of the query which is to execute.But the expectation is only alert detail not all the data frm db,which cause huge space issue in our server too.
The Pega0005 alert is triggered when the elapsed time for a query to the PegaRULES database exceeds a threshold setting (the default setting is 0.5 seconds). This setting helps you recognize when queries are inefficiently designed and when data is being loaded indiscriminately. To learn more about the Pega0005 Alert please refer to the "Understanding the PEGA0005 alert - Query time exceeds limit" article on the PDN (https://pdn.pega.com/performance/understanding-the-pega0005-alert-query-time-exceeds-limit). The best practice is to investigate the source of the Alert and resolve the underlying performance issue. Following this Best Practice is especially important in Production Environments. You can also reduce the number of times the Pega0005 Alert is logged by adjusting the threshold settings. The following PDN Forum Post discusses how to do this: "How to set higher threshold value for a specific web-service/DB call" (https://pdn.pega.com/forums/pega0005/how-to-set-higher-threshold-value-for-a-specific-web-servicedb-call). Keep in mind however, that although increasing the threshold time will reduce the number pf Pega0005 Alerts logged into the Alert Log it does not resolve the underlying performance issue.
Thanks for that.But I had already gone through thses docs.Here the problem is while alert is logging in to the Alert log,It is fetching all the DB records with exception.Usually alert should contain only the activity name,SQL and alert details.
But here All DB records also fetching by this alert.
How can I restrict that alert with few deatails?I dont want to fecth all DB records while throwing this Alert.From the logs i have identified the activity which is causing this and found Query also.Ithe query i can do some improvement for avaoiding the alert.But once if again the alert has thrwon due to this activity,this will start to fetch all DB records.
The Alert Log will capture the SQL statement that triggered the Pega0005 Alert along with vital PAL Statistics but it should not be capturing the actual Result Set (data) generated by the SQL into any Log files. If in fact the Alert Log or any other Log is including the Result Set (data) generated by the SQL it may be because the developer who wrote the Activity is using the Log-Message method to write the data into a Log file or there is something wrong with the configuration of PRPC or Pega 7. Please confirm that the activity is not writing the Result Set (Data) to any logs.
This may be the result of some configuration problem that is not readily apparent and will require a more thorough review of your System Logs to properly troubleshoot. Please submit a Service Request (SR) so one of our technicians can work with you. You can do so by accessing the new My Support Portal (https://pdn.pega.com/support/my-support-portal).