Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Expose external Elasticsearch URL to Kibana plugins #139405

Closed
richkuz opened this issue Aug 24, 2022 · 3 comments
Closed

Expose external Elasticsearch URL to Kibana plugins #139405

richkuz opened this issue Aug 24, 2022 · 3 comments
Labels
old Used to help sort old issues on GH Projects which don't support the Created search term. Team:Core Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc

Comments

@richkuz
Copy link
Contributor

richkuz commented Aug 24, 2022

Describe the feature:

Please expose the external Elasticsearch URL value to Kibana plugins.

Describe a specific use case for the feature:

Enterprise Search provides an Elasticsearch API curl example usage in the UI.

image

Enterprise Search uses decodeCloudId to parse an Elasticsearch URL when running on Cloud. If there is no Cloud URL, Enterprise Search defaults to https://localhost:9200. More ideal would be an API to pull the external ES URL from config, but such a setting is not available to plugins today.

This feature also blocks this use case in the Elasticsearch dev console:
#77464

More context: #119862 (comment)

@richkuz richkuz added the Team:Core Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc label Aug 24, 2022
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-core (Team:Core)

@pgayvallet
Copy link
Contributor

More ideal would be an API to pull the external ES URL from config

Following the discussions we had with the team during our previous grooming: If the external ES URL the one that Kibana uses to connect to ES, when in a Cloud environment? Or is Kibana accessing ES via an internal URL instead?

@TinaHeiligers TinaHeiligers added the old Used to help sort old issues on GH Projects which don't support the Created search term. label Oct 8, 2024
@TinaHeiligers
Copy link
Contributor

We haven't heard any other requests for exposing the external ES Url to kibana plugins and I'm closing this issue as stale.
We can reopen if the need arises again.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
old Used to help sort old issues on GH Projects which don't support the Created search term. Team:Core Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc
Projects
None yet
Development

No branches or pull requests

4 participants