How to config automation-specific job logs cleanup?

Check out under System Configuration > System Cleanup Cleaning Up FME Flow Logs and Other Files 

• you can change max age
• or better still, duplucate existing tasks and add a filter to met your requirements to clean up certain items more frequently

​@j.botterill Thanks for your reply, but unfortunately I do not think the provided filter options will work for our case.

Our job logs are stored under $(FME_SHAREDRESOURCE_LOG)engine/current/jobs with filenames such as job_<jobid>.log (for example, job_221935.log). The available filter options only appear to support filtering by whether the filename ends with, or does not end with, a specified string.

Since the log filename only contains the job ID and does not include the automation name, automation ID, or automation frequency, the filter cannot identify which logs belong to hourly, daily, or monthly automations. Therefore, it does not appear possible to apply different cleanup schedules to different automations using these filename-based filter options alone.

There’s an open idea for exactly this: 

Please vote! 😃

​@redgeographics I did. 😀

Just wondering if there is any workaround before that idea is implemented.

It looks like there is not much we can do through the current system cleanup configuration.

I am considering creating a workflow to track log files and clean them up based on a user-defined run frequency.