[Ingest] Find solution to removing index pattern error messages when no matching index exists

[neptunian]

#61257 improves the messaging but for most use cases it might make sense to remove this error altogether. It's not uncommon after the Ingest Manager is released that this scenario occurs. When the user installs a package we create some index patterns by default that the user might not actually be using but go look at. We also install dashboards and if they click on one where no data yet exists, it looks like this:

Or when viewing an index pattern in the Management app

This is not ideal as we don't want to create indexes that aren't being used, but for now, we will send a document on index pattern creation time to create the index and suppress this error.

[elasticmachine]

Pinging @elastic/ingest-management (Team:Ingest Management)

[neptunian]

@ruflin I am thinking to send a document to an index name that the pattern will match but will make its purpose clear to us. Something like:

PUT logs-index-pattern-placeholder/_doc/1
{
}

[ruflin]

👍 One issue with the above proposal is that it will match the logs-*-* template and I think it should better not as we might enforce a timestamp there. Perhaps logs-index_pattern_placeholder instead?