You can configure index lifecycle management (ILM) policies to automatically manage indices according to your performance, resiliency, and retention requirements. For example, you could use ILM to:
- Spin up a new index when an index reaches a certain size or number of documents
- Create a new index each day, week, or month and archive previous ones
- Delete stale indices to enforce data retention standards
When you enable index lifecycle management for Beats or the Logstash Elasticsearch output plugin, ILM is configured automatically. You can modify the default policies through Kibana Management or the ILM APIs.
To automatically back up your indices and manage snapshots, use snapshot lifecycle policies.