Skip to main content
This content is now archived and is no longer updated. Progress is not calculated. Pega Cloud instances are disabled, and badges are no longer awarded.

PegaRULES Log Analyzer (PLA)

PegaRULES Log Analyzer (PLA)

Regular monitoring of log files during development and production helps ensure your application is operating properly. The PegaRULES Log Analyzer (PLA) is a standalone web application that developers and system administrators can use to view summaries of console logs.

Use the PLA to test new or reconfigured Pega applications during user acceptance testing (UAT), performance and stress testing, and immediately after deployment into a production environment. Testing reconfigured applications during UAT, during performance testing, and right after deployment is important because performance, stability, and scaling issues are most likely to occur during these times.

The PLA consolidates and summarizes three types of logs — ALERT, PEGA, and Garbage Collection (GC) — from individual Pega JVM server nodes in your application system. The log data provides key information about operational and system health.

View log information to quickly identify, diagnose, and remedy issues that may be degrading or compromising your application:

  • To monitor performance, review the ALERT log. The ALERT log contains diagnostic messages that identify individual system events that exceed performance thresholds or failures. Alert messages contain a set of field values that identify the alert, the conditions that caused it, and the state of system when it occurred. The ALERT log supports performance-related monitoring.
  • To monitor system stability, review the PEGA log. The PEGA log gathers system errors, exceptions (with their stack trace statements), debug statements, and any other messages not specified as alerts. The PEGA log can contain messages created by your activities as well as messages created by standard rules. The PEGA log is also referred to as the console log or system log.
  • For insight into how your Pega application is using memory, monitor the JVM garbage collection log.

Each node on a Pega system produces two log files, the ALERT Log and the PEGA log. The PEGA log contains messages created since the most recent start of the server. The log file is usually named PegaRULES-YYYY-MMM-DD.log. The date portion of the name indicates the date the application server was recently started (on the current node).

For more information about the PLA, refer to:

For more information about alerts, refer to:

For information about how to customize logs, refer to:

This Topic is available in the following Module:

We'd prefer it if you saw us at our best.

Pega Academy has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice