You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Multi-tenancy support for Kibana. Either through object replication or Kibana syncing or whatever term, or means, that would provide this.
Describe a specific use case for the feature:
Elasticsearch provides cross cluster search but Kibana can only connect to one Elasticsearch cluster. If I would like to create a single interface to search all of my data this is possible due to cross cluster search.
However, when I have multiple locations and want them to be self-supporting for example when using Kibana alerting, I would need to setup a Kibana instance for each location. Each instance could still be connected and configured to support the CCS so this would work fine. But from a user perspective you would like to give them a single interface with all of their queries, visualizations and dashboards.
As described I would like multiple locations to be self-supporting. In case of a network failure between data-centers or any other cause the internal data-center should still be functioning (alerting, queries, visualizations) without external support or resources.
Kibana does not support Cross Cluster Replication. In the current situation I would need to create a Kibana replicator that exports all objects from one Kibana instance to another Kibana instance to keep the Kibana instances in sync.
The text was updated successfully, but these errors were encountered:
Describe the feature:
Multi-tenancy support for Kibana. Either through object replication or Kibana syncing or whatever term, or means, that would provide this.
Describe a specific use case for the feature:
Elasticsearch provides cross cluster search but Kibana can only connect to one Elasticsearch cluster. If I would like to create a single interface to search all of my data this is possible due to cross cluster search.
However, when I have multiple locations and want them to be self-supporting for example when using Kibana alerting, I would need to setup a Kibana instance for each location. Each instance could still be connected and configured to support the CCS so this would work fine. But from a user perspective you would like to give them a single interface with all of their queries, visualizations and dashboards.
As described I would like multiple locations to be self-supporting. In case of a network failure between data-centers or any other cause the internal data-center should still be functioning (alerting, queries, visualizations) without external support or resources.
Kibana does not support Cross Cluster Replication. In the current situation I would need to create a Kibana replicator that exports all objects from one Kibana instance to another Kibana instance to keep the Kibana instances in sync.
The text was updated successfully, but these errors were encountered: