After connecting Kibana to a local ES client Marvel doesn't have data

monitoring

#1

I have a cluster with 3 masters, 2 datas and 2 kibana's all on individual virtual machines (ubuntu).

Everything was working until we decided to put an elasticsearch client node (cluster and kibana load balancer) on our Kibana server.

The flow goes like this.

Kibana > Client ES node > ES cluster.

Any ideas why I woudn't be getting Marvel data with this change?


(Steve Kearns) #2

I haven't heard of anything like this before - certainly that's a configuration that I have seen work in the past.

What versions are you running? Can you confirm that the new client ES node has successfully joined the cluster and has the marvel-agent installed as well?

Thanks,
Steve


(Mark Walkom) #3

Do the indices exist, check with _cat/indices.
Also check your ES logs to see if there is being reported there.


(system) #4