You can configure {ilm} ({ilm-init}) policies to automatically manage indices according to your performance, resiliency, and retention requirements. For example, you could use {ilm-init} 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
You can create and manage index lifecycle policies through {kib} Management or the {ilm-init} APIs. Default {ilm} policies are created automatically when you use {agent}, {beats}, or the {ls} {es} output plugin to send data to the {stack}.
|
Tip
|
To automatically back up your indices and manage snapshots, use snapshot lifecycle policies. |