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.

Configuring logger settings

Updated on March 11, 2021

This content applies only to On-premises and Client-managed cloud environments

In a development environment, you can enable logging by adding the appropriate logger settings in the prlog4j2.xml file. In a production environment, most standard logging is set to warn and should remain at this level. For more information on log levels, see the Apache Log4j documentation.

  • Open the prlog4j2.xml file and make the necessary edits. This file is located together with the prconfig.xml file. For more information, see Modifying the prconfig.xml file.
  • You can also set log levels in Dev Studio by clicking ConfigureSystemLogsLogging level settings and selecting the logger name and level.
For example:

In the example provided below, logging is set to show warning messages for System Pulse. You can control the level of logging by setting it to another level.


<Logger name="SystemPulse" additivity="false" level="warn">
	<AppenderRef ref="SECURITYEVENT"/>   
</Logger>

Related articles

Enabling decision management services

Tags

Pega Platform 8.4 Decision Management

Have a question? Get answers now.

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

Visit the Support Center

Did you find this content helpful?

Yes
No

Want to help us improve this content?
Suggest an edit

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

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us