LinkedIn
Copied!

Table of Contents

Separate logging for schema operations

Version:

Only available versions of this content are shown in the dropdown

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"> <PatternLayout> <Pattern>%d [%20.20t] [%10.10X{pegathread}] [%20.20X{app}] (%30.30c{3}) %-5p %X{stack} %X{userid} - %m%n</Pattern> </PatternLayout> <Policies> <TimeBasedTriggeringPolicy /> <SizeBasedTriggeringPolicy size="250 MB"/> </Policies> <DefaultRolloverStrategy max="20"/> </RollingRandomAccessFile> <Logger name="SchemaDesignerLogger" level="info" additivity="false"> <AppenderRef ref="RollingRandomAccessFileDBOPERATIONS"/> </Logger>

If you have configured database operations for a separate log, you can view the log file by clicking Configure System Operations Logs Log Files PegaDBOPERATIONS in the header of Dev Studio.

Have a question? Get answers now.

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