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
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...
The text was updated successfully, but these errors were encountered:
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?
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...
The text was updated successfully, but these errors were encountered: