-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
Comments
@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. |
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? |
@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. |
Pinging @elastic/es-ui |
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. |
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.
The text was updated successfully, but these errors were encountered: