[role="xpack"]
[[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

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}.

[role="screenshot"]
image:images/ilm/index-lifecycle-policies.png[]

[TIP]
To automatically back up your indices and manage snapshots, use
<<automate-snapshots-slm,snapshot lifecycle policies>>.

* <<example-using-index-lifecycle-policy>>
* <<getting-started-index-lifecycle-management>>
* <<overview-index-lifecycle-management>>
* <<ilm-concepts>>
* <<set-up-lifecycle-policy>>
* <<migrate-index-allocation-filters>>
* <<index-lifecycle-error-handling>>
* <<start-stop-ilm>>
* <<ilm-with-existing-indices>>
* <<skipping-rollover>>
* <<index-lifecycle-and-snapshots>>
* <<index-lifecycle-management-api>>
* <<ilm-actions>>

--
include::example-index-lifecycle-policy.asciidoc[leveloffset=-1]

include::ilm-tutorial.asciidoc[]

include::../indices/index-mgmt.asciidoc[]

include::ilm-overview.asciidoc[]

include::ilm-concepts.asciidoc[]

include::ilm-actions.asciidoc[]

include::set-up-lifecycle-policy.asciidoc[]

include::../data-management/migrate-index-allocation-filters.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[]
