Skip to main content
This content has been updated. Click here to continue your progress in the latest version.

Pega application monitoring 

Pega application monitoring

Many organizations have application performance monitoring (APM) tools to track and report on application performance and responsiveness. While these tools can report on data such as memory and CPU usage on your database and application servers, they do not provide detailed information about the health of the Pega application itself.

Pega provides two tools designed to monitor and provide recommendations on how to address alerts generated by the Pega application. These tools complement any APM tools you might use to give you a complete picture of your Pega application's health.

  • Autonomic Event Services (AES) – AES monitors on-premise applications. AES is installed and managed on-site.
  • Predictive Diagnostic Cloud (PDC) – Pega PDC is a Pega-hosted Software as a Service (SaaS) application that monitors Pega Cloud™ applications. PDC can also be configured to monitor on-premise applications.

Admin Studio - Pega Admin Studio is a role-based authoring and management environment focused on system operations such as agents, queues, and APIs. Admin Studio is targeted at experienced system administrators.

The tool you use depends on your monitoring requirements and if you want to customize the monitoring application.

The following table compares differences between AES and PDC.

Feature PDC AES
Hardware provisioning Pega Customer
Installation and upgrades Pega Customer
Ability to customize Upon request Fully customizable
Release schedule Quarterly Yearly
Communication with monitored nodes One-way Two-way
Active system management (restart agents, listeners, quiesce node) Not available Available

Both AES and PDC monitor the alerts and health activity for multiple nodes in a cluster. Both send you a scorecard that summarizes application health across nodes. From an architecture standpoint, the most notable difference is that AES interacts with the monitor node to allow you to manage processes on the monitored nodes, such as restarting agents and quiescing application nodes.

You can use AES or PDC to monitor development, test, or production environments. For example, you can set up AES to monitor a development environment to identify any troublesome application area before promoting higher environments.

For more information on AES and PDC, see the following resources:

System health monitoring

Monitoring the health of the system is as important as the performance of an application. Pega Platform™ provides many options to assess the system health on different parameters. Lead system architects (LSAs) must be aware of the Pega tools to monitor the system's health:

Performance data

Pega Platform continuously generates data about the performance without impacting system performance. Performance data can be obtained using PAL. PAL provides information such as rule/server/RDB elapsed time, CPU statistics, and other I/O operations. Analysis of the data helps to understand the cause of delay in navigation from one view to another. Performance information about the execution of activities, when rules, and data transforms can be obtained by Performance Profiler.

Pega Platform continually generates performance data (PAL) and issues alerts if the application exceeds the thresholds that you have defined.

Lightweight lists data

Lightweight lists require less CPU memory and less processing than standard page lists. Lightweight lists are recommended wherever possible. To get the list of rules which do not use lightweight list, go to Configure > System > Performance > Rules not using lightweight lists landing page which displays a tab for each type of rule. The rules that do not use the lightweight lists report help to identify rules where the lightweight list can be used. It can be also controlled using the DSS setting (for example, clipboard/lightWeightList/enableForCorePRPCRules and clipboard/lightWeightList/enableForCustomerRules). An LSA must be aware of the limitations and usage of lightweight lists to improve the performance of the application.

System state data

System state data that contains information such as data and work index status, the queues, and their status, is presented in JSON format. System state data can be downloaded from Admin Studio or it can be accessed using the REST API. Comparing the state of the system over time helps to determine what might have changed on the system that caused the problem.

JVM data

The version of JDK and configuration of Heap Memory and its increment have an impact on the memory performance and overall system throughput. Virtual memory allocation is an important system design consideration. JVM vendor recommendations should be followed and the required memory should be allocated to avoid some of the common problems like the out-of-memory exception.

Services data

Pega application services can be tracked separately to know the impact those services have on Pega application performance. The PEGA0011 alert and the Service-PAL log file help to identify issues related to services. Changing the parameters of lengthy services or parsing rules can be considered to improve the performance after analyzing the alert and service-PAL log files.
For more information about the health monitoring Pega tools, see Monitoring the health of your system.

The following image shows a sample JSON of the system state for the FSG application.


If you are having problems with your training, please review the Pega Academy Support FAQs.

Did you find this content helpful?

100% found this content useful

Want to help us improve this content?

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