Marvel location missing for plugin installation?

monitoring

(Jason) #1

When I run:

/opt/elasticsearch/bin/plugin install marvel

I get the following output:

-> Installing marvel...
Trying https://download.elastic.co/elasticsearch/release/org/elasticsearch/plugin/marvel/2.3.2/marvel-2.3.2.zip ...
ERROR: failed to download out of all possible locations..., use --verbose to get detailed information

I can do a manual wget from https://download.elasticsearch.org/elasticsearch/marvel/marvel-2.3.2.tar.gz

I'm guessing the plugin command is looking for a zip file in that location (not a tgz)?

It looks as though something is not getting built and copied over within the Marvel/ES build process?


(Jason) #2

Nevermind.

I was not running the plugin with Kibana. An err on my part in reading the details.


(Chris Earle) #3

Just to be clear for anyone that comes across this post later, starting with Marvel 2.x, it was split into two plugins:

  1. marvel-agent, which is used by Elasticsearch
  2. marvel, which is used by Kibana

So they're installed separately within their respective applications:

$ ${ES_HOME}/bin/plugin install marvel-agent
$ ${KIBANA_HOME}/bin/kibana plugin --install elasticsearch/marvel/latest

FYI, this will be simplified in Elasticsearch 5 and Kibana 5, so lookout for blog posts that discuss "x-pack" (e.g., the Elastic{ON} Keynote).


(system) #4