Hi,

Thank you for posting your questions in Product Support Community. 

You can go ahead and try setting system property log4j2.debug to TRACE to get detailed internal log4j logs during configuration and rollover. logging.apache.org/log4j/2.x/faq.html#troubleshooting Also, have you tried asking on the log4j user mailing list?

Also, for more details, please see the  Custom Delete action supported by the Rollover File appender: https://logging.apache.org/log4j/2.x/manual/appenders.html#CustomDeleteOnRollover

Hope this helps.

Thanks,

Debraj

Hi Debraj,

I have used the below Delete tag in pega log4j2.xml and didnt work.

<RollingRandomAccessFile  name="PEGA" fileName="${sys:pega.logdir}_PegaRULES.log" filePattern="${sys:pega.logdir}_PegaRULES-%d{MM-dd-yyyy}-%i.log.gz">

Hi All,

Can anyone tried this configuration or any other way to delete the old logs from the server? using PegaRules log xml file.

Regards,

Anandh

I think it should be:

</Policies>

<DefaultRolloverStrategy max="20">

<!--Delete log more then 30days-->

  <Delete basePath="${sys:pega.logdir}" maxDepth="1">

      <IfFileName glob="warrantyauthoring_*.log.gz" />

      <IfLastModified age="30d" />

     </Delete>

</DefaultRolloverStrategy>

</RollingRandomAccessFile> 

Guess this can be easily done by RHEL log rotation option or keeping one cron job