Which alerts will be triggered before nodes getting down
Hi ,
If server nodes are getting down what kind of alerts will be triggered and how to identify the root cause from the alerts . I mean, if any long process is running for more time on the nodes, this may cause , specific nodes may slow down, so how to identify this kind of issues at node level.
Thanks in Advance.
Thank you kakul for the response. so my understanding is , if i found this alerts in AES or logs, that means nodes may slow down after some times. My understanding correct?
one more thing, because of response time exceeds threshold limits(PEGA020 i think) this kind of alerts are more in the system, it may also will effect the nodes to get slow down .
The thing is, some times i can see some nodes are getting slow down,so just i want to analyze because of some rules its causing this issue or any other reasons may causing this slow down of the nodes? how can i start my analysis on this kind of issues.
The PEGA0020 alert is triggered when a response was received from an external system or database after a connector request was sent to that system, but the interaction time exceeds the threshold value.
reference: https://pdn.pega.com/pega0020-alert-total-connect-interaction-time-exce…
You can see which particular rule is the culprit from the Pega Rules logs.
The following is the article on how to understand the alert logs. Apply loggers to that particular rule to get more info.
https://pdn.pega.com/understanding-alert-log-message-data/understanding…
Hi,
It differs with each case, if it is out of memory you can see PEGA0028 alert, or it down due to the long requestors it is PEGA0019 alerts.
For more information on alerts, please find below pdn article.
https://pdn.pega.com/performance-alerts-security-alerts-and-autonomic-e…
Pega0004,0005,006,007 are related to DB time. 005 is a very commonly observed alert. It comes when Query Time Exceeds the limit. 0019 is another alert, comes when it encounters a long-running requestor. 004 if excess data retrieved from DB. 001 related to http interaction time.
Look at https://pdn.pega.com/performance-alerts-security-alerts-and-autonomic-e…
https://blog.pega.com/blog/thinking-ahead-pega-alerts-every-developer-s…