Using Curator vs basic linux script + cron job to delete /var/log/elasticsearch files

I've setup Curator to delete metricbeat indices older than 14 days within our cluster. After reading through the Curator documentation is there any real need to use Curator to delete /var/log/elasticsearch logs or is a basic shell script run with a Cron job the only thing really needed for removing logs? Seems like using Curator just adds an unnecessary step to the process.

Curator doesn’t remove logs. It helps manage indices in Elasticsearch which can contain logs. Curator cannot be used to manage anything in a file path, like /var/log/elasticsearch.

Sounds good, thats what I was gathering after reading through the docs but just wanted to check. Appreciate the quick response Aaron. Enjoy the rest of your day.

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.