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

Kibana multi-tenancy support #212180

Open
poppelaars opened this issue Feb 22, 2025 · 0 comments
Open

Kibana multi-tenancy support #212180

poppelaars opened this issue Feb 22, 2025 · 0 comments
Labels
needs-team Issues missing a team label

Comments

@poppelaars
Copy link

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.

@botelastic botelastic bot added the needs-team Issues missing a team label label Feb 22, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs-team Issues missing a team label
Projects
None yet
Development

No branches or pull requests

1 participant