Skip to main content

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.

Support Article

Some alerts are not written to the alert log file



Some alerts are not written to the alert log file even though the alert buffer is set to maximum size.

Error Messages

Not Applicable

Steps to Reproduce

Put Pega under heavy load, then review alert log file.

Root Cause

Working as intended.  The alert logger will drop alerts if the buffer is full to prevent possible performance issues.


If the system must have all alerts written, even at the cost of slowdown, perform the following local-change:

Set parameter "blocking" in prlogging.xml to "true". 
This can cause processing to pause while AES sends alerts, so ensure to set it back to false after running the test. This setting should ensure that, if the buffer is full, AES will wait instead of dropping messages. With that setting on false, AES will drop messages if the buffer is full.
Suggest Edit

Published January 31, 2016 - Updated October 8, 2020

Did you find this content helpful? Yes No

Have a question? Get answers now.

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

We'd prefer it if you saw us at our best.

Pega Community 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
Contact us