Question
3
Replies
5312
Views
TATA CONSULTANCY SERVICES
Posted: May 22, 2016
Last activity: May 23, 2016
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 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