Getting N_CriticalErrorNotification as unhealth in ping service.

In the ping service, getting the status as unhelathy for the node and with the details



N_CriticalErrorNotification



failure

Don’t find any additional details in the log. Don’t see any Out of Memory issue or File system issue.

Not able to find the rootcause but the node is up and running.

Any idea where to get the additional information?

@rrudramu When your ping service health check displays N_CriticalErrorNotification and the node is marked as unhealthy, it typically indicates a critical error, often related to an Out of Memory (OOM) issue. Unfortunately, if you do not find additional details in the logs, it may be due to the limitations of the node health checks, which catch only about 70 to 80 percent of OOM errors. In such cases, it is advisable to submit a support case through My Support Portal for further assistance, especially if your environment is a Pega Cloud environment.

Pega Ping service FAQs