ilm error-handling - index name does not match pattern

[jguay]

Currently the troubleshooting guide for ILM mentions my-index needs to be named my-index-000001 for rollover API to be able to roll over the index which is correct but lacking some context about what causes or solves this

Can reviewer fix hyperlinks to use appropriate asciidoc format ? I wanted to link to :

• https://www.elastic.co/guide/en/elasticsearch/reference/8.11/getting-started-index-lifecycle-management.html#ilm-gs-alias-bootstrap (usually the cause of the error is when user skipped this step)
• https://www.elastic.co/guide/en/elasticsearch/reference/8.11/docs-reindex.html (as an index cannot be renamed reindex will likely be needed after fixing the issue)

[github-actions]

Documentation preview:

• ✨ Changed pages

[elasticsearchmachine]

@jguay please enable the option "Allow edits and access to secrets by maintainers" on your PR. For more information, see the documentation.

[elasticsearchmachine]

Pinging @elastic/es-docs (Team:Docs)

[elasticsearchmachine]

Pinging @elastic/es-data-management (Team:Data Management)

[abdonpijpelink]

I've left a few suggestions that add the links.

[jguay]

Thank you @abdonpijpelink for the 3 corrections - feel free to merge or approve and I'll merge if all is good now

[abdonpijpelink]

LGTM from the docs side.

[leemthompo]

Important

Elastic documentation is migrating to Markdown for version 9.0+. See the migration guide for details.

ℹ️ What's happening?

• Starting January 29, we will start closing all unmerged documentation PRs targeting main/master
• We're migrating from AsciiDoc to Markdown for 9.0+
• 9.0 docs will be frozen from January 29 until February 20 2024
• NOTE: PRs that include both code and documentation changes will remain open

What do I need to do?

For <=8.x docs:

1. Rebase your PR to target the relevant 8.x branch instead
2. The content can remain in AsciiDoc format

For 9.0+ docs:

Option 1:

• Draft docs in Markdown
• Once migration freeze ends, find the relevant page in the new docs system and use the edit options to submit your changes

Option 2:

• Open an issue in elastic/docs-content

💡 Need help?

1. For Elasticians: Ask in #docs Slack channel
2. For external contributors: Open an issue in elastic/docs-content