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

 Anandh Palanisamy (Anandh Palanisamy)
Ford Motor Company

Ford Motor Company
US
Anandh Palanisamy Member since 2013 62 posts
Ford Motor Company
Posted: Mar 1, 2019
Last activity: Apr 26, 2019
Posted: 1 Mar 2019 22:06 EST
Last activity: 26 Apr 2019 16:09 EDT
Closed

Deleting PegaRules log file more then 30days old

Hi,

Did anyone tried deleting old PegaRules log using Delete tag through prlog4j2 file.

I have tried and its not deleting those logs.

Regards,

Anandh

***Edited by Moderator Marissa to update platform capability tags****

To see attachments, please log in.
Pega Platform
Case Management
System Administration

Posted: 6 years ago
Posted: 3 Mar 2019 13:14 EST
Debraj Tarafder (tarad1) Senior Pega Support Associate
Pegasystems Inc.
IN

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

To see attachments, please log in.
Posted: 6 years ago
Posted: 4 Mar 2019 12:55 EST
Anandh Palanisamy (Anandh Palanisamy)
Ford Motor Company

Ford Motor Company
US

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">

Show More

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">

<PatternLayout>
<Pattern>%d [%20.20t] [%10.10X{pegathread}] [%20.20X{tenantid}] [%20.20X{app}] (%30.30c{3}) %-5p %X{stack} %X{userid} - %m%n</Pattern>
</PatternLayout>
<Filters>
                <!--Deny message logged under ALERT log level-->
                <ThresholdFilter level="ALERT" onMatch="DENY" onMismatch="NEUTRAL"/>
            </Filters>
<Policies>
<TimeBasedTriggeringPolicy />
<SizeBasedTriggeringPolicy size="25 MB"/>
</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>
 
</RollingRandomAccessFile> 
 
 
Regards,
Anandh

Show Less
To see attachments, please log in.
Posted: 6 years ago
Posted: 26 Apr 2019 3:34 EDT
Souf Yc (SoufY686)
It

It
NL

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" />

Show More

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> 

 


Show Less
To see attachments, please log in.
Posted: 6 years ago
Posted: 26 Apr 2019 16:09 EDT
Sreecharan Babu Challagundla (SREECHARAN)
Cognizant Technologies Solutions US
Sreecharan Babu Challagundla
Cognizant Technologies Solutions US
US

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

To see attachments, please log in.

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