Question
Understanding the PEGA0044 alert
Hi,
1) How PEGA0044 alert can be addressed and what actions should we take to resolve this ?
2) Is it advisable to suppress this alert ?
| Alert Information | |
|---|---|
| MsgID | PEGA0044 |
| Initial Action | NA |
| Last Action | NA |
| Alert Occurred at | May 21, 2016 6:22:19 PM |
| Operator was | NA |
| Occurred on Node | ServerNode1 created 2013-07-24 16:25:30.317 GMT |
| KPI Value | 301 |
| KPI Threshold | 300 |
| Problem Correlation | EXCP0001 |
| Line | Reached threshold limit for message ID: EXCP0001, will send again after Sat May 21 18:22:24 MST 2016 |
Thanks
Hari Kumar Alampuru
Hi Harish,
Thanks for your reply !
Have searched the mentioned settings in both DSS & Prconfig but not able to locate. If those settings are not defined in either DSS or prconfig, will there be any OOTB/default settings that gets picked up at Run-Time ?
In our Production Application, this alert gets triggered generally for EXCP0001 and found a relevant support article which says :
https://pdn.pega.com/support-articles/excp0001-alerts-are-throttled-pega0044-hiding-some-exceptions
SUMMARY
Too many EXCP0001 alerts from the same source cause all EXCP0001 alerts to be suppressed using the throttle mechanism documented in alert PEGA0044.
RESOLUTION
An enhancement request has been created for consideration by Pega Product Management.
The request is to except EXCP0001 alerts or to allow their throttle values to be configurable.
FDBK-13639 has been created.
This enhancement request to decouple EXCP0001 from the Pega0044 throttle monitoring/to provide a specific setting to configure the throttle values for EXCP0001 alert.
Do we know in which Pega Product version this Enhancement request is planned to be incorporated.
Hi Hari,
You won't find the prconfig/DSS by default, you need to add the below entries in prconfig.xml to configure the no of time & time period as specified in the PDN link https://pdn.pega.com/understanding-pega0044-alert-reached-threshold-limit-message-id-pegaxxx-will-send-again-after-date
Like I said, If the set limit is reached, the actual alert will be suppressed and the support article which you have found is that, EXCEP0001 alerts are being throttled by PEGA0044 alerts and some of the EXCEP0001 are being hidden which will eliminate exceptions that might be needed for review. The enhancement request is that there should be a mechanism to exclude certain alerts from being throttled(like EXCEP0001), rather than setting a global throttle limit. Looks like the enhancement request is not yet prioritized and waiting for evaluation.
However, the SA article/Enhancement request is for a different purpose where the user doesn't want to suppress EXCEP0001 alerts by regular throttle mechanism.
BR//
Harish
Hi Hari,
PEGA0044 is fired after an alert has occurred too many times in a given time window, If the number of a particular kind of alert (EXCP0001, PEGA0005, etc) exceeds the threshold you get the PEGA0044 alert.
Throttle alerts (PEGA0044) uses two prconfig settings to define/control it.
If some alert crosses say 1000 times (maxAlertCountInTimePeriod) in 10 mins (maxAlertCountTimePeriodMinutes) PRPC sends PEGA0044 alert. If the set limit is reached, the actual alert will be suppressed to allow system administrators to fix the root cause without any impact caused by the alerts themselves.
Hence, PEGA0044 alert tells you which alert has occurred too many times so that we can try to investigate on the causes for that particular alert.
BR//
Harish