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

Read-only Tribe nodes and Kibana #5391

Closed
bodgit opened this issue Mar 11, 2014 · 2 comments
Closed

Read-only Tribe nodes and Kibana #5391

bodgit opened this issue Mar 11, 2014 · 2 comments

Comments

@bodgit
Copy link

bodgit commented Mar 11, 2014

I have multiple ES clusters in different datacenters fed by Logstash and I would like to use one or more tribe nodes in a central location federating across them so I can have a single Kibana instance to search with, (I understand from elastic/kibana#22 how this should work).

Disabling write access seems to make sense here except the problem of the kibana-int index which is the only index that needs to be writeable from the point of view of a Kibana user. It would be useful maybe to be able to disable writes globally to the tribes except for that particular tribe/index. At the moment I guess I have to run with writes enabled everywhere?

Although I can't help thinking the write access should possibly be enforced by the remote clusters rather than on each tribe node...

@bodgit
Copy link
Author

bodgit commented Apr 8, 2014

Looks like #5501 goes most of the way to fixing this.

@bodgit bodgit closed this as completed Apr 8, 2014
@ghost
Copy link

ghost commented Jul 8, 2014

bodgit, I am facing a somewhat similar situation and would appreciate your help. I have a Tribe node as a central location with a central Kibana, but I am unable to save dashboards on the Kibana instance. Could you possibly take a look at my issue and tell me how you resolved this?

elastic/kibana#1347

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant