The elasticsearch version I am using is 2.3.
I just installed an elasticsearch cluster with 3 nodes,1 Master and data node, another data node, and a client node.
And I installed marvel in the client node.
It complains:
It's OK, I got the name of the marvel-agent plugin wrong anyway ;). I probably should have figured that out from the context of the output.
I'm guessing you only have the single node then, and that it's the same node that you are pointing Kibana at. Do you see the marvel indices in your cluster? Assuming you're using the default indices:
http://localhost:9200/.marvel-es-data-1/_search
http://localhost:9200/.marvel-es-*/_search
Also, check the time on your server and make sure it lines up with the time in your browser. If it's more than 10 minutes apart, you'll see the no data error.
Just going to leave this here just in case anyone is as stupid as me...
I too had this problem, twice in fact. The first time, the times on the nodes we out. FW rule to the NTP server was the culprit. The second occasion was a script that was supposed to update just one index, updated all:
Same problem here.
Wanted to put my resolution in as well for anyone else.
Check your license. Marvel installs with 30 days free. On top of that you can keep it free for a year at a time. If your license is expired you'll see no Marvel data as well as information in the cluster log telling you (telling me) exactly what the issue was.
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.