- Issue created by @mparker17
-
mparker17 →
committed 6f9d4fd2 on 3538452-server-status-msg-more-useful
Issue #3538452: Make Server connection status more useful
-
mparker17 →
committed 6f9d4fd2 on 3538452-server-status-msg-more-useful
- 🇮🇳India pooja saraah Chennai
Patch proposal suggestion:
Update the Search API server connection routine to retrieve and expose Elasticsearch cluster details: cluster name, node version, and health status.
On connection failure, capture and display the HTTP response code and error message.
Modify the admin UI rendering (Controller + Twig) to conditionally display the enriched status or failure details.
Ensure all added strings are translatable and update the .pot/.po translations accordingly. - Merge request !102Issue #3538452: Make Server connection status more useful → (Open) created by mparker17
- 🇨🇦Canada mparker17 UTC-4
I had apparently pushed to the wrong issue fork in #2... I've now created a merge request in the correct issue fork: I apologize for the confusion.
I had been hesitating on this patch because it requires additional permissions...
- additional cluster-level permission:
monitor
- additional index-level permissions:
maintenance
,monitor
That being said, when I was writing the guide on setting up an API key with a role descriptor → , I included these permissions, so it's probably okay for now.
Probably a better solution would be to test whether or not we have these permissions before trying to access data that requires it (i.e.: because we could selectively display information based on what the API key we're connecting with has permission to view). Ideally, Elasticsearch has a has-privileges API and a get application privileges API we could use to query this; another option could be to try getting the data and catching 403 errors, but the Elasticsearch Connector module doesn't yet have infrastructure to support either of those approaches.
- additional cluster-level permission: