Not sure about the downsides of running Kibana as a site plugin, but here's how I got it to work so that others can perform create and run our initial evaluations with ease.
The Elasticsearch bin/plugin command doesn't seem to read the location into which I have put my configuration, and it's not necessary anyway. But it was very helpful to determine the exact directory structure. First, I store the current versions of Elasticsearch and kibana in the /opt tree. The config directory contains updated versions of ES configurations that are suggested for use by a deployment, but the actual versions used will be outside of this directory tree and will likely be maintained by Puppet or similar tool. The plugins directory is where I have configured ES to look for plugins; as Kibana3 shows, the version of the plugins does not need to be tied directly to a specific version of ES even though this is the case when the plugin uses the Java API and not the REST API. $ ls -1 /opt/elk/current bin config elasticsearch-1.2.1 kibana-3.1.0 logs plugins So "installing" Kibana-3.1.0 as a site plugin was a simple matter of: $ mkdir /opt/elk/current/plugins/kibana3 $ ln -s /opt/elk/current/kibana-3.1.0 /opt/elk/current/plugins/kibana3/_site Verifying the link: $ ls -l /opt/elk/current/plugins/kibana3/_site lrwxr-xr-x 1 brian admin 33 Jun 11 14:16 /opt/elk/current/plugins/kibana3/_site -> /opt/elk/current/kibana-3.1.0 Now it's just as if Kibana was installed directly into the plugins directory, but it didn't need to be stored there physically. 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/5f1102fe-b3c3-4a5a-b754-eef7f5168ba8%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
