In our QA environment, we have two servers running Elasticsearch in the same cluster, which effectively means we have two nodes. Right now, we have Kibana set up on only one of the servers, and it's currently configured to use that sever's ES instance for it's connection to our data. When ES needs to be cycled or otherwise brought down on the box, Kibana breaks because it cannot connect.
After about 30 minutes of searching, this is the closest thing I could find my issue: #22. But the distinction is I want Kibana to still pay attention only to a single cluster, but have data served to it from multiple nodes.
Is it possible to configure Kibana to set multiple ES servers/nodes for it's connection to the ES cluster? If so, could the documentation be updated somewhere to reflect how to do this? Thanks.
In our QA environment, we have two servers running Elasticsearch in the same cluster, which effectively means we have two nodes. Right now, we have Kibana set up on only one of the servers, and it's currently configured to use that sever's ES instance for it's connection to our data. When ES needs to be cycled or otherwise brought down on the box, Kibana breaks because it cannot connect.
After about 30 minutes of searching, this is the closest thing I could find my issue: #22. But the distinction is I want Kibana to still pay attention only to a single cluster, but have data served to it from multiple nodes.
Is it possible to configure Kibana to set multiple ES servers/nodes for it's connection to the ES cluster? If so, could the documentation be updated somewhere to reflect how to do this? Thanks.