# Kibana4 and Elasticsearch cluster

**URL:** https://discuss.elastic.co/t/kibana4-and-elasticsearch-cluster/34660
**Category:** Kibana
**Created:** [November 16, 2015, 9:57am UTC](https://discuss.elastic.co/t/kibana4-and-elasticsearch-cluster/34660 "2015-11-16T09:57:52Z")
**Posts on this page:** 1
**Showing post:** 4

<div class="post-metadata">

### Author: ![magnusbaeck](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/magnusbaeck/32/44943_2.png) [@magnusbaeck](https://discuss.elastic.co/u/magnusbaeck)
#### Post date: [November 16, 2015, 12:01pm UTC](https://discuss.elastic.co/t/kibana4-and-elasticsearch-cluster/34660/4 "2015-11-16T12:01:52Z")

</div>

I think Kibana's `elasticsearch_url` option is singular, i.e. it needs to be exactly one URL. As you've noticed this creates a single point of failure. To mitigate that you could e.g. use HAproxy to front of two or more ES instances and point Kibana to the HAproxy hostname/port.

---

_[View the full topic](https://discuss.elastic.co/t/kibana4-and-elasticsearch-cluster/34660)._