[Logs UI] Improve error handling when using undefined remote cluster in source settings

[miltonhultgren]

📓 Summary

🚫 Blocked until #159128 is implemented.

The current implementation for the Logs UI setting page doesn't work well when a user configures an invalid index pattern, not handling properly a failing response (HTTP status 500) from the server:

[2022-02-14T12:33:41.213+00:00][ERROR][http] ResponseError: [object Object]: security_exception: [no_such_remote_cluster_exception] Reason: no such remote cluster: [remote_cluster]

👣 Reproduction steps

1. Enter the Logs UI Settings page.
2. Fill in an index name pattern that includes a remote cluster that is not configured, like unknown_remote:metricbeat-*
3. Save the settings and reload the page

✔️ Acceptance criteria

1. No Logs UI page should fail to load due to a misconfigured index source
2. When saving the settings, warnings should be shown if there is an unknown remote cluster being used
3. The error in Logs UI should not include the raw error, instead we should display a user-friendly message about what is wrong in the config

[elasticmachine]

Pinging @elastic/infra-monitoring-ui (Team:Infra Monitoring UI)

[pmeresanu85]

@smith I created a new Milestone label to tag all ERs which would be candidates for archiving.
Archiving doesn't mean the idea is rejected, it just means we shouldn't actively pursue this idea.

[tonyghiani]

Related to #144882

[tonyghiani]

To gracefully handle this issue where a name pattern is not available or unreachable, we can apply the same behaviour implemented for the Metrics setting for the same scenario, solved with this PR.

[elasticmachine]

Pinging @elastic/obs-ux-logs-team (Team:obs-ux-logs)

[achyutjhunjhunwala]

Anyone picking this issue, the only pending issue here is with the Logs Setting page

[tonyghiani]

I've reworded the issue to be correctly scoped for the Logs UI settings. The suggested approach to implement a solution is still valid.

[gbamparop]

Related to #180936

[gui-elastic]

@gbamparop Is it possible to assign someone to this issue and do we have any ETA to fix it?

[gbamparop]

@gui-elastic configuring log sources with index patterns and data views through the log settings page is now deprecated in favour of the relevant Kibana advanced setting. This setting is visible in the log settings page but can only be changed from Stack Management.

Both the log settings and log stream pages will be removed in 9.0 (#203996, #204115) where this will no longer be an issue.

However, the issue is present in 8.17 when configuring the log sources through Kibana advanced settings and navigate to the log settings page.

Screen.Recording.2025-01-23.at.12.40.45.mov

A workaround is to update the Kibana advanced setting by removing the remote cluster that doesn't exist. Does this work for you?

We could investigate potential fixes and consider a fix for 8.x.

[weltenwort]

• ✅ done in 8.x
• 🔙 backported to 8.18
• 🔙 backported to 8.17