Skip to main content

This content is closed to future replies and is no longer being maintained or updated.
Links may no longer function. If you have a similar request, please write a new post.

Question

 Akash Sinha (AkashS1762)
VirtusaPolaris

VirtusaPolaris
IN
AkashS1762 Member since 2016 28 posts
VirtusaPolaris
Posted: Nov 15, 2018
Last activity: Nov 15, 2018
Posted: 15 Nov 2018 1:30 EST
Last activity: 15 Nov 2018 11:00 EST
Closed

RegexFilter does not match multiline log messages

After upgrade from Pega Marketing 7.2.1 to 7.3.1, updated log4j2.xml for custom loggers.

<RollingRandomAccessFile name="PEGA" fileName="/somepath/PegaRULES.log" filePattern="/somepath/PegaRULES-%d{MM-dd-yyyy}-%i.log.gz">
<PatternLayout>
<Pattern>some pattern</Pattern>
</PatternLayout>
<Filters>
<!--Deny message logged under ALERT log level-->
<ThresholdFilter level="ALERT" onMatch="DENY" onMismatch="NEUTRAL"/>
<RegexFilter regex=".*ABC_Logger.*" onMatch="DENY" onMismatch="NEUTRAL"/>
</Filters>
If the log message contains "\n", the message is going to PegaRULES.log instead of custome logger. It works fine if there is no line break.
To see attachments, please log in.
Pega Marketing
Low-Code App Development
Updates

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

Pega Collaboration Center 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