# \[HELP\] cannot automate rollovers with filebeat

**URL:** <https://discuss.elastic.co/t/help-cannot-automate-rollovers-with-filebeat/261809>\
**Category:** Beats\
**Tags:** filebeat\
**Created:** [January 21, 2021, 3:06pm UTC](https://discuss.elastic.co/t/help-cannot-automate-rollovers-with-filebeat/261809 "2021-01-21T15:06:01Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![lachezar.uzunov](https://avatars.discourse-cdn.com/v4/letter/l/ecae2f/32.png) [@lachezar.uzunov](https://discuss.elastic.co/u/lachezar.uzunov)\
**Post date:** [January 21, 2021, 3:06pm UTC](https://discuss.elastic.co/t/help-cannot-automate-rollovers-with-filebeat/261809/1 "2021-01-21T15:06:01Z")

</div>

Hello everyone.

I am trying to create automation rollup system to archive and delete checkpoint firewall logs based on conditions.  
The problem I face is not being able to automate my filebeat to write to the new created index (after rollover).

Example to make things clear:

I have index: checkpoint-000001  
When it reaches 30mb of data (for testing purpose) it creates new index: checkpoint-000002 but my filebeat is still writing to the first one. When the delete action occurs, it renews the index from scratch.

I can't seem to find a way to automate things on config standpoint. Hope I was clear and thank you in advance. 🙂

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [February 18, 2021, 5:06pm UTC](https://discuss.elastic.co/t/help-cannot-automate-rollovers-with-filebeat/261809/2 "2021-02-18T17:06:06Z")

</div>

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