Six weeks after you deliver your application to production, your users report that the application slows down in the afternoon. The application is almost completely unresponsive for some users shortly after
3:00 P.M. Other users do not experience this problem until later in the day. You do not have access to the Production environment, but you do have access to AES. The production environment has three nodes and a load balancer. You need to resolve this issue because a new division of the organization will start using the application next month.
How do you begin your research to diagnose the cause of the reported performance issue?
- Look at the performance profile and DB Trace output from each node.
- Observe the cluster and node status on the Enterprise Health Console.
- Review guardrail warnings in the development environment to determine if any rules with warnings moved to production.
- Download the alert log file from each node and analyze the contents in the Pega Log Analyzer.
Answer(s): D
Explanation:
Analyzing alert logs using the Pega Log Analyzer (PLA) is a critical step in diagnosing performance issues. The alert logs contain detailed information about performance alerts, which can help identify bottlenecks or specific rules causing delays. By reviewing the logs from each node, you can pinpoint the time and nature of the performance issues and take corrective actions.
Reference:
Pega Troubleshooting: Pega Log Analyzer
Pega Performance: Monitoring and Troubleshooting
Reveal Solution Next Question