123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354 |
- [role="xpack"]
- [testenv="basic"]
- [[index-lifecycle-management]]
- = {ilm-init}: Manage the index lifecycle
- [partintro]
- --
- 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
- When you enable {ilm} for {beats} or the {ls} {es} output plugin,
- {ilm-init} is configured automatically.
- You can modify the default policies through {kib} Management or the {ilm-init} APIs.
- [TIP]
- To automatically back up your indices and manage snapshots,
- use <<getting-started-snapshot-lifecycle-management,snapshot lifecycle policies>>.
- * <<overview-index-lifecycle-management>>
- * <<ilm-concepts>>
- * <<getting-started-index-lifecycle-management>>
- * <<ilm-actions>>
- * <<set-up-lifecycle-policy>>
- * <<index-lifecycle-error-handling>>
- * <<start-stop-ilm>>
- * <<ilm-with-existing-indices>>
- * <<skipping-rollover>>
- * <<index-lifecycle-and-snapshots>>
- --
- include::ilm-overview.asciidoc[]
- include::ilm-concepts.asciidoc[]
- include::ilm-tutorial.asciidoc[]
- include::ilm-actions.asciidoc[]
- include::set-up-lifecycle-policy.asciidoc[]
- include::error-handling.asciidoc[]
- include::start-stop.asciidoc[]
- include::ilm-with-existing-indices.asciidoc[]
- include::ilm-skip-rollover.asciidoc[]
- include::ilm-and-snapshots.asciidoc[]
|