Marvel agent exporter

monitoring

(Sunil Chaudhari) #1

Hi,
I installed marvel plugin as below:

ES 3 nodes cluster: marvel-agent on all 3 nodes
marvel-2.3.4.tar.gz on Kibana host.
Restarted kibana and ES.
When I hit URL http://KIbana-Host:5601, it show Status: RED and under installed plugin it shows

   plugin:elasticsearch 	Service Unavailable
    plugin:marvel 	Waiting for Elasticsearch 

In ES logs it says:

[2016-07-28 13:49:49,569][INFO ][marvel.agent.exporter    ] [sit-master-data-node-0] skipping exporter [default_local] as it isn't ready yet
[2016-07-28 13:49:59,573][INFO ][marvel.agent.exporter    ] [sit-master-data-node-0] skipping exporter [default_local] as it isn't ready yet
[2016-07-28 13:50:09,574][INFO ][marvel.agent.exporter    ] [sit-master-data-node-0] skipping exporter [default_local] as it isn't ready yet
[2016-07-28 13:50:10,552][WARN ][discovery                ] [sit-master-data-node-0] waited for 30s and no initial state was set by the discovery

What is the reason for this. In another environment I followed same steps and it works.

br,
Sunil


(Chris Earle) #2

Hi Sunil,

    plugin:elasticsearch        Service Unavailable
    plugin:marvel               Waiting for Elasticsearch

This indicates that Kibana is waiting for a connection to Elasticsearch. It has nothing to do with Marvel. Ensure that Kibana is talking to the right Elasticsearch node(s).

[2016-07-28 13:49:49,569][INFO ][marvel.agent.exporter    ] [sit-master-data-node-0] skipping exporter [default_local] as it isn't ready yet
[2016-07-28 13:49:59,573][INFO ][marvel.agent.exporter    ] [sit-master-data-node-0] skipping exporter [default_local] as it isn't ready yet
[2016-07-28 13:50:09,574][INFO ][marvel.agent.exporter    ] [sit-master-data-node-0] skipping exporter [default_local] as it isn't ready yet
[2016-07-28 13:50:10,552][WARN ][discovery                ] [sit-master-data-node-0] waited for 30s and no initial state was set by the discovery

This indicates that Elasticsearch is not ready yet because it's waiting for master quorum. Ensure that your 3 nodes are properly configured to communicate with each other.


(system) #3