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.

Separate logging for schema operations

Updated on April 5, 2022

Operations performed using the Schema Tools landing page, including Pega Cloud schema operations, can be logged to a separate file from the PegaRules log file. To enable logging to a separate file, add the following appender to the prlog4j2.xml file.

<RollingRandomAccessFile name="RollingRandomAccessFileDBOPERATIONS" fileName="${sys:pega.tmpdir}/PegaDBOPERATIONS.log" filePattern="${sys:pega.tmpdir}/PegaDBOPERATIONS-%d{MM-dd-yyyy}-%i.log.gz">
		<Pattern>%d [%20.20t] [%10.10X{pegathread}] [%20.20X{app}] (%30.30c{3}) %-5p %X{stack} %X{userid} - %m%n</Pattern>       
		<TimeBasedTriggeringPolicy />
		<SizeBasedTriggeringPolicy size="250 MB"/>
	<DefaultRolloverStrategy max="20"/>
<Logger name="SchemaDesignerLogger" level="info" additivity="false">
	<AppenderRef ref="RollingRandomAccessFileDBOPERATIONS"/>         

If you have configured database operations for a separate log, you can view the log file by clicking ConfigureSystemOperationsLogsLog FilesPegaDBOPERATIONS in the header of Dev Studio.

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