In particular Exceptions logged in PegaRULES log files are sent to PDC for analysis: Exceptions – Exceptions are sent to Predictive Diagnostic Cloud for analysis (DEBUG or INFO statements are not sent). You can view exceptions by looking at the error lines in the PegaRULES log file. Exceptions can contain some contextual data that is a subset of the fields sent for alerts.
I am trying to configure PDC for log monitoring and trying to understand if it has a capability wherein it alerts the platform support team on exceptions/errors like Java out of memory, requestor lock, etc.
As of now we have custom scripts deployed for proactive monitoring but we are trying to understand if PDC would be a good replacement of it.
PDC does not do log monitoring per se, but it does receive a lot of events that are also reflected in the logs. PDC gets every alert and exception, and also receives a health status message from the management daemon every two minutes. Platform 73 (and maybe 72) send PEGA0086 messages for Requestor Lock Exceptions, and PDC knows how to read a PEGA0086 so that it gives you a reasonable explanation for why the session was locked, and has an optional notification scorecard specifically for PEGA0086. The management daemon sends PDC a health status message every two minutes. The health status message includes average CPU utilization over two minutes and current heap usage percentage. PDC will trigger alarms / notification scorecards if heap or cpu exceed threshold. PDC team has started adding logic to recognize specific common exceptions and translate them into actionable advice; we welcome more patterns / stories for our backlog. Feel free to contact me directly to review your existing monitoring and talk about what PDC can do in comparison.