Kibana is just a javascript web application (it stores some stuff in a
shard called .kibana in the ES cluster as the data) , so, to make it
HA, you just have to run a nginx with reverse proxy with any number of
kibana apps. just treat is a normal static website.
On Wed, Apr 15, 2015 at 1:31 PM, vikas gopal vikas.hafig@gmail.com wrote:
Sorry if I was not clear , I want 2 things
-
How I can make Kibana highly available , I mean I want same setup as ES
has if one down other will take over so my confusion is if I install kibana
on 2 servers and use one load balancer on top of these 2 instances how 2
kibana instances will be in sync.
Not sure if this is a valid solution .If you have any other approch or
solution to achieve this please suggest.
-
I do not want to provide "http://localhost:5601" or
"http://ipaddress:5601" to the user . I want to provide a fancy name some
thing like "http://security-dashboard:5601". Now again how it's possible
with the multiple servers.
On Wednesday, April 15, 2015 at 10:47:39 AM UTC+5:30, Mark Walkom wrote:
And what do you want help on?
On 15 April 2015 at 00:38, vikas gopal vikas...@gmail.com wrote:
Hi Experts,
Need your valuable suggestion here . I have following setup and it is
working fine.
-
2-ES nodes (in Cluster handled by AWS load balancer)
-
1-LS node (push data to any ES)
-
1-Kibana Node (will get index from any of the ES )
-
One load balancer for ES instances.
Now I want to extend it further . I want Kibana highly available like I
have setup for ES if one server is down then second will take over . So by
this, I mean I am planning to install kibana on 2 servers to make it highly
available and want to use single address rather localhost:5601. So that that
common address I can provide to the user.
--
You received this message because you are subscribed to the Google Groups
"elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to elasticsearc...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/a7997db4-8e61-4c95-b059-b1723494090b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups
"elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/88b05749-d441-4f4d-a931-375ec8adb7bb%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CAJygYd3q0Lrwr5hPf5a8XAjmpoHNhaONmEzV5zFPCYkz7j8ZkQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.