Question
cognizant
IN
Last activity: 28 Jun 2024 7:19 EDT
How to check the Performance of our application in the Pega.
How to check the Performance of our application in the Pega.
Accepted Solution
Updated: 28 Jun 2024 7:19 EDT
Eclatprime Digital Private Limited
IN
To check the performance issue we can use below steps.
DBTrace: DBrace is a feature in the Performance Analysis Tool (PAL) that creates a detailed log of calls to the PegaRULES database. DBTrace displays SQL statements sent to the database and the time spent for each operation.
PAL: This data is stored in “PAL counters” or “PAL readings.” PAL stands for Performance Analyzer and is a collection of counters and timer readings, stored in the requestor, that an application developer could use to analyze performance issues in a system.
PAL Features
- Add Reading
- Add Reading with Clipboard Size
- Reset Data
- Save Data
- Start DBTrace
- DBTrace Options
- Start Profiler
- Show Graph
- My Alerts
Alerts: During application processing, Process Commander writes to the performance alert log a sequence of text entries called alert messages that identify mainly performance-related issues or errors. The performance alert log is usually named PegaRULES-ALERT-YYYY-MMM-DD log.
To check the performance issue we can use below steps.
DBTrace: DBrace is a feature in the Performance Analysis Tool (PAL) that creates a detailed log of calls to the PegaRULES database. DBTrace displays SQL statements sent to the database and the time spent for each operation.
PAL: This data is stored in “PAL counters” or “PAL readings.” PAL stands for Performance Analyzer and is a collection of counters and timer readings, stored in the requestor, that an application developer could use to analyze performance issues in a system.
PAL Features
- Add Reading
- Add Reading with Clipboard Size
- Reset Data
- Save Data
- Start DBTrace
- DBTrace Options
- Start Profiler
- Show Graph
- My Alerts
Alerts: During application processing, Process Commander writes to the performance alert log a sequence of text entries called alert messages that identify mainly performance-related issues or errors. The performance alert log is usually named PegaRULES-ALERT-YYYY-MMM-DD log.
AES: Exceptions are processed in a similar way as alerts. When a Process Commander server generates exceptions they are sent by SOAP to the AES system. The system parses the exceptions and stores the records in the pegaam_exception table in the AES database. Based upon how often an exception occurs and the system events that triggered those exceptions, AES aggregates these records into work objects called AES exception items. These items are written to the AES database in the pegaam_exception_work table.
Eclatprime Digital Private Limited
IN
Monitoring and checking the performance of a Pega application involves using a combination of built-in tools and features within the Pega platform. These tools help you analyze various aspects of performance, including response times, system utilization, and resource usage. Here are some key tools and methods to check the performance of your Pega application:
1. Performance Analyzer (PAL)
The Performance Analyzer (PAL) is a powerful tool in Pega that helps you measure the performance of specific interactions or requests.
How to Use PAL:
-
Access PAL:
- Log in to your Pega application.
- Navigate to
Dev Studio > Configure > System > Performance > PAL.
-
Start PAL:
- Click on the
Resetbutton to reset the counters. - Click on the
Startbutton to start recording.
- Click on the
-
Perform Actions:
- Perform the actions or transactions you want to analyze.
-
Stop PAL:
- Click on the
Stopbutton to stop recording. - Click on the
Add Readingbutton to capture the performance data.
- Click on the
-
Analyze PAL Data:
Monitoring and checking the performance of a Pega application involves using a combination of built-in tools and features within the Pega platform. These tools help you analyze various aspects of performance, including response times, system utilization, and resource usage. Here are some key tools and methods to check the performance of your Pega application:
1. Performance Analyzer (PAL)
The Performance Analyzer (PAL) is a powerful tool in Pega that helps you measure the performance of specific interactions or requests.
How to Use PAL:
-
Access PAL:
- Log in to your Pega application.
- Navigate to
Dev Studio > Configure > System > Performance > PAL.
-
Start PAL:
- Click on the
Resetbutton to reset the counters. - Click on the
Startbutton to start recording.
- Click on the
-
Perform Actions:
- Perform the actions or transactions you want to analyze.
-
Stop PAL:
- Click on the
Stopbutton to stop recording. - Click on the
Add Readingbutton to capture the performance data.
- Click on the
-
Analyze PAL Data:
- Review the collected data, which includes statistics like interaction counts, database queries, CPU usage, and more.
2. Performance Profiler
The Performance Profiler helps you identify performance bottlenecks in your Pega application by profiling the execution of rules and other processing.
How to Use Performance Profiler:
-
Access Performance Profiler:
- Log in to your Pega application.
- Navigate to
Dev Studio > Configure > System > Performance > Profiler.
-
Start Profiler:
- Click on the
Startbutton to begin profiling.
- Click on the
-
Perform Actions:
- Execute the actions or processes you want to profile.
-
Stop Profiler:
- Click on the
Stopbutton to end profiling. - Download the profiler log to analyze the captured data.
- Click on the
-
Analyze Profiler Data:
- Use tools like Pega Log Viewer or external tools to examine the profiler data and identify performance bottlenecks.
3. Tracer Tool
The Tracer tool allows you to trace the execution of rules and processes in real-time, helping you debug and analyze performance issues.
How to Use Tracer:
-
Access Tracer:
- Log in to your Pega application.
- Navigate to
Dev Studio > Configure > System > Operations > Tracer.
-
Configure Tracer Settings:
- Select the rulesets, events, and other options you want to trace.
-
Start Tracer:
- Click on the
Startbutton to begin tracing.
- Click on the
-
Perform Actions:
- Execute the actions or processes you want to trace.
-
Stop Tracer:
- Click on the
Stopbutton to end tracing. - Analyze the trace results to identify performance issues.
- Click on the
4. System Management Application (SMA)
The System Management Application (SMA) provides a comprehensive view of the health and performance of your Pega system, including JVM statistics, requestor details, and more.
How to Use SMA:
-
Access SMA:
- Log in to your Pega application.
- Navigate to
System > Operations > System Management Application.
-
Monitor JVM and Node Health:
- Check JVM statistics like memory usage, garbage collection, and thread counts.
-
Analyze Requestor Information:
- View active requestors and their statistics, including response times and resource usage.
-
Monitor Queue Processors:
- Check the status and performance of queue processors and agents.
5. Pega Predictive Diagnostic Cloud (PDC)
Pega Predictive Diagnostic Cloud (PDC) is a cloud-based monitoring and diagnostic service that provides real-time insights into the performance and health of your Pega applications.
How to Use PDC:
-
Access PDC:
- Log in to Pega Predictive Diagnostic Cloud using your credentials.
-
Monitor Application Performance:
- View dashboards and reports that provide insights into application performance, system health, and potential issues.
-
Analyze Alerts and Events:
- Examine alerts and events generated by Pega, including performance warnings and error messages.
-
Use Diagnostic Tools:
- Utilize diagnostic tools within PDC to drill down into specific performance issues and identify root causes.
6. Database Performance Monitoring
Monitoring the database performance is crucial for overall application performance. Use database tools to monitor and optimize database queries and performance.
How to Monitor Database Performance:
-
Database Monitoring Tools:
- Use database-specific monitoring tools like Oracle Enterprise Manager, SQL Server Management Studio, or PostgreSQL tools.
-
Analyze Query Performance:
- Examine slow-running queries and optimize them by creating indexes, rewriting queries, or tuning the database.
-
Review Database Logs:
- Check database logs for errors, slow queries, and other performance-related issues.