Skip to main content

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

This content has been archived and is no longer being updated.

Links may not function; however, this content may be relevant to outdated versions of the product.

Monitor the Pega log and Alert log to improve performance

Updated on September 22, 2020

 This presentation is part of the Designing and Building for Performance Self-Study Course.



Before deciding that an application is ready to promote to the next level (UAT, Pre-Production, or Production), check the PegaRULES Alert log file and the PegaRULES Error log file.

The ALERT log file should be empty if MyAlerts has been checked along the way.  If not, determine which ALERTS are continuing to be presented and why.

More importantly, check the Pega error log file since many errors can occur that do not significantly affect the user experience – at least that is what it may seem when unit testing.  A failed call to a connector, a failed rule execution, a null pointer exception, or a missing or inconsistent rule can have a significant impact on the quality of the application.

Aside from being a PRPC best practice, it is important to ensure there are no errors in the log file from a performance perspective because:

  • Logging the errors and producing stack traces is resource intensive
  • It is difficult to see performance related messages when the log file is riddled with other errors
  • Some errors may have the side effect of slowing down the system

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