Skip to main content

         This documentation site is for previous versions. Visit our new documentation site for current releases.      

Monitoring the health of your system

Updated on August 25, 2021

Pega Platform provides a variety of tools to help you monitor the health of your system. It is important to monitor the system logs to be alerted of possible problems. For ways to identify and resolve system issues, refer to the topics listed below.

  • Predictive Diagnostic Cloud

    The Predictive Diagnostic Cloud (PDC) is a secure Software as a Service (SaaS) offering that runs on Pega Cloud and actively gathers, monitors, and analyzes real-time performance and health indicators from all active Pega Platform applications. PDC also predicts potential system performance and business logic issues, and notifies business stakeholders and IT administrators with remediation suggestions before they impact the business.

  • Downloading the system state for a cluster or node

    To help troubleshooting, download the system state data for the current state or a previously saved state into a JSON file. You can download the system state data for a single node or for the whole cluster. For example, you can compare the state of the system over time to determine what might have changed on the system that caused the problem.

  • Viewing the JVM in use on your server

    Pega Platform runs within a Java Virtual Machine (JVM) on the servers that make up the system.

  • Tracking system utilization for a requestor session with Performance Analyzer

    Use the Performance Analyzer (PAL) to view cumulative system usage statistics for your requestor session.

  • Tracking rule utilization for a requestor session with Performance Profiler

    Use the Performance Profiler landing page to obtain a detailed trace of performance information about the execution of activities, when condition rules, and data transforms executed by your requestor session. The Profiler traces every execution (in all threads) of rules of these three types in all rulesets, and creates a separate output file for each thread in your session.

  • Viewing statistics for services in the SERVICES-PAL log

    To see performance statistics for services, view the SERVICES-PAL log.

  • Identifying rules not using lightweight lists

    Use the Lightweight Lists utility to report on rules in your application that are using page lists where they could use lightweight lists instead. You can improve system performance by using lightweight lists. The utility searches list view rules and summary view rules, plus Obj-Browse and LookupList activities.

  • Reporting on rule usage snapshots

    Pega Platform maintains statistics about the number of rule executions since startup. Create and view reports about these shutdown statistics to understand which rules execute most often, and which execute rarely or not at all. Viewing these statistics can help you identify the causes of variations in system performance.

  • Deploying static content to an edge server

    You can deploy static content to multiple web servers, also known as edge servers, to improve responsiveness in a large production system. In Web pages, the term static content usually refers to image files (.jpg, .png, .gif, and .swf), style sheet files (.css), and JavaScript files (.js) that do not frequently change. You can deploy static content to multiple web servers, also known as edge servers, to improve the responsiveness of your production system.

  • Lengthy service operations

    Pega Platform adds a PEGA0011 alert to the Alert log when a service operation or parse rule operation takes an unusually long time. The line identifies the requestor, the service, and the value of the performance statistic. View these alerts so that you can take action to improve system performance.

  • Verifying that an instance is running

    You can verify that a Pega Platform instance is running by pinging the instance.

  • Generating requestor reports for system-wide usage from the Log-Usage class

    The system captures performance details for each requestor once each hour and at logoff. You can view these details, aggregated or by operator ID, by using standard reports. These reports include assemblies and compilations by node, performance by ruleset list, and performance data for your operator for the past week.

  • Identifying loaded module versions

    The module version report provides information about the classes (modules) in the system, the versions of the modules, the update dates of the module versions, and the corresponding node ID. You can generate the module version report to identify discrepancies in the versions of the modules (classes) across Pega Platform nodes, which helps engineers when they debug problems.

  • Licenses

    A license defines input parameters that support collecting and reporting usage data. By using a license, you can demonstrate compliance with your software license agreement.

  • System Performance landing page

    From the System Performance landing page, you can access tools to help you manage system performance.

  • Previous topic Automating the runtime context management of background processes
  • Next topic Predictive Diagnostic Cloud

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us