[Logs UI, Metrics UI] Data errors can block access to the settings page

[jasonrhodes]

We're aware of mapping issues that occur in a user's configured indices can cause some error messages in the UI. These mapping issues should not block access to the settings page, which is where a user would be able to update their source configuration to point to different indices, to resolve the mapping problems.

Can we confirm whether it's possible for a user to get into this state with an API error that isn't related to the settings page, in both the Logs UI and the Metrics UI? And if so, we should fix it in both places.

Related: we should consider exposing a validated API for updating the source configuration for cases like these, to prevent a user from becoming in an unfixable state.

[elasticmachine]

Pinging @elastic/logs-metrics-ui (Team:logs-metrics-ui)

[weltenwort]

it's possible #64021 already fixed this

[jasonrhodes]

To get in this state:

Turn on filebeat but don't run the setup command (don't install the index template)

or

Add a document to a new, untemplated, filebeat-whatever-* index with a @timestamp, message, and event.dataset fields.

Load the UI and you should see this error in the stream view but be able to get to the Settings tab. At the very least, you should get to the /settings URL if you go to it directly.