I couldn't find any official documentation or best practices, though it
seems implied in the Kibana installation instructions, but is there any
word on whether or not Kibana3 should or should not live on a node in the
ES cluster? Thoughts on pros and cons of doing so?
Pro - one less box to stand up
Con - performance impacts on the ES node who drew the short straw?
Doesn't really matter as Kibana itself uses very little resources, the
queries are still going to your cluster. You do need to consider security
etc though.
You can even run it as an elasticsearch "plugin" if you put it in the
plugins directory and the access it via $host:9200/_plugin/kibana.
I couldn't find any official documentation or best practices, though it
seems implied in the Kibana installation instructions, but is there any
word on whether or not Kibana3 should or should not live on a node in the
ES cluster? Thoughts on pros and cons of doing so?
Pro - one less box to stand up
Con - performance impacts on the ES node who drew the short straw?
Thanks for your answer, Mark. What would you recommend as the most secure
approach? I'm just trying to formulate some sort of argument, however
minimal, of Kibana on an ES node or not. I am assuming that *not *having
Kibana on the ES node is the more secure setup, as if it were, users would
be accessing the cluster directly, versus some external box that
communicates with the ES cluster under controlled ports.
Andrew
On Tuesday, August 19, 2014 6:11:12 PM UTC-4, Mark Walkom wrote:
Doesn't really matter as Kibana itself uses very little resources, the
queries are still going to your cluster. You do need to consider security
etc though.
You can even run it as an elasticsearch "plugin" if you put it in the
plugins directory and the access it via $host:9200/_plugin/kibana.
On 20 August 2014 05:01, Andrew Ruslander <andrew.r...@gmail.com
<javascript:>> wrote:
I couldn't find any official documentation or best practices, though it
seems implied in the Kibana installation instructions, but is there any
word on whether or not Kibana3 should or should not live on a node in the
ES cluster? Thoughts on pros and cons of doing so?
Pro - one less box to stand up
Con - performance impacts on the ES node who drew the short straw?
Thanks for your answer, Mark. What would you recommend as the most secure
approach? I'm just trying to formulate some sort of argument, however
minimal, of Kibana on an ES node or not. I am assuming that *not *having
Kibana on the ES node is the more secure setup, as if it were, users would
be accessing the cluster directly, versus some external box that
communicates with the ES cluster under controlled ports.
Andrew
On Tuesday, August 19, 2014 6:11:12 PM UTC-4, Mark Walkom wrote:
Doesn't really matter as Kibana itself uses very little resources, the
queries are still going to your cluster. You do need to consider security
etc though.
You can even run it as an elasticsearch "plugin" if you put it in the
plugins directory and the access it via $host:9200/_plugin/kibana.
I couldn't find any official documentation or best practices, though it
seems implied in the Kibana installation instructions, but is there any
word on whether or not Kibana3 should or should not live on a node in the
ES cluster? Thoughts on pros and cons of doing so?
Pro - one less box to stand up
Con - performance impacts on the ES node who drew the short straw?
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.