Laura, The simplest way is to install Kibana as a site plug-in on the same node on which you run Elasticsearch. Not the best way from a performance and security perspective, but certainly the easiest way to start with an absolute minimum of extra levers to pull and knobs to turn, so to speak.
So what does that really mean, a "site plugin"? Assume you configure Elasticsearch to look for plugins within the /opt/elk/plugins directory. Then you unpack the Kibana3 distribution within /opt/kibana3. That means you'll see the following files within /opt/kibana3/kibana-3.1.0: app build.txt config.js css favicon.ico font img index.html LICENSE.md README.md vendor So then create the /opt/elk/plugins/kibana3 directory. Then: $ ln -s /opt/kibana3/kibana-3.1.0 /opt/elk/plugins/kibana3/_site Now when you start ES and point it to the correct configuration file which in turn points it to the plugins directory as described above, Kibana will be available at the following URL (assuming you're on the same host; change localhost as needed, of course): http://localhost:9200/_plugin/kibana3/ Hope this helps! Brian -- 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+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/59b1ac76-d3a5-4b63-bdc6-f617ef8c0627%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
