-
Task
-
Resolution: Fixed
-
L3 - Default
-
None
-
None
-
70
Context:
To ensure scalability of the event ingestion we need a rollover mechanism to keep index size manageble. See
https://www.elastic.co/blog/managing-time-based-indices-efficiently
https://www.elastic.co/guide/en/elasticsearch/reference/master/indices-rollover-index.html
AT:
- to ensure scalability of the event ingestion a rollover is performed (preferable a combination of time and size/doc count rollover)
- the rollover is controlled from the optimize application, no x-pack functionality of elasticsearch is used