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

Console should be able to query any cluster configured in kibana.yml #11866

Closed
epixa opened this issue May 17, 2017 · 6 comments
Closed

Console should be able to query any cluster configured in kibana.yml #11866

epixa opened this issue May 17, 2017 · 6 comments
Labels
enhancement New value added to drive a business result Feature:Console Dev Tools Console Feature Feature:Dev Tools high hanging fruit Team:Kibana Management Dev Tools, Index Management, Upgrade Assistant, ILM, Ingest Node Pipelines, and more

Comments

@epixa
Copy link
Contributor

epixa commented May 17, 2017

When more than one cluster is configured in kibana.yml, for example when you have a data and an admin cluster configured, or when you have a separate X-Pack monitoring cluster configured, users should be able to select which of those clusters they want to query when using Console. This doesn't mean that arbitrary clusters will be supported, but when Kibana already knows about a cluster for a given purpose, then querying that cluster through Console can be extremely useful for debugging purposes.

Since plugins can create arbitrary clusters, the big challenge here is defining an abstraction that ensures that whenever a cluster is registered from any plugin it is also exposed through Console.

@jbudz
Copy link
Member

jbudz commented May 17, 2017

@epixa same issue #8955?

@epixa
Copy link
Contributor Author

epixa commented May 17, 2017

@jbudz Not really. After re-reading #8955, I realized that the user is actually asking for Console to be able to query any cluster that appears in X-Pack monitoring, which isn't going to be possible since Kibana doesn't actually have connection/authentication information for those clusters. I incorrectly assumed when I first read it that they were asking for the behavior that I describe here. I'm going to close that one out.

@framegrace
Copy link

I have all the monitoring data on a separate cluster, I point kibana to that cluster for monitoring. That means that I can only use that kibana instance for monitoring?
I have to setup another instance to be used by devconsole and the rest of the tools?

@epixa
Copy link
Contributor Author

epixa commented Aug 9, 2017

@framegrace If you have kibana set up for one cluster and are sending monitoring data to a separate monitoring cluster, then if you wanted to use the capabilities of kibana as a whole on that monitoring cluster, you will need a separate kibana instance for it.

@cjcenizal cjcenizal added Feature:Console Dev Tools Console Feature Team:Kibana Management Dev Tools, Index Management, Upgrade Assistant, ILM, Ingest Node Pipelines, and more and removed :Management DO NOT USE labels Mar 29, 2019
@elasticmachine
Copy link
Contributor

Pinging @elastic/es-ui

@cjcenizal
Copy link
Contributor

At the present moment, Elastic expects administrators to attach a Kibana instance to no more than one deployment in order to manage and analyze its data. One deployment, >=1 Kibana(s), one Console per Kibana. Closing this until a different approach becomes a priority.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New value added to drive a business result Feature:Console Dev Tools Console Feature Feature:Dev Tools high hanging fruit Team:Kibana Management Dev Tools, Index Management, Upgrade Assistant, ILM, Ingest Node Pipelines, and more
Projects
None yet
Development

No branches or pull requests

6 participants