Hello,

I noticed the following behavior using the SifitingAppender/SizeAndTimeBasedRollingPolicy functionnality (in 1.0.13 an 1.1.8 versions)

When a user is logging in the application, we put his user identifier as context value (MDC) in order to have one log file by user activity.
If a user won't connect anymore in the application, his logs (and his archives) will never be cleared since the appender will be never used again.

I did some tests with the new "totalSizeCap" property (on 1.1.8 version) but since it's an appender-level configuration, the problem still the same.

It would be nice to have to possibility to say to the framework there is a global parameter for application-level (delay limit or size limit) after which a remover has to execute a cleaning task.

Could you confirm me that this parameter doesn't already exists ? (I didn't find it in the documentation or existing requests).

Regards,

Franck R