ES reachable from curl but not from Marvel/Sense

Question

I am in the 2 hour of my Elastic Search immersion. I successfully installed ES with Marvel (with marvel.agent.enabled: false in config/elasticsearch.yml) and was ab

Answer 1

In your ES cluster logs (in one node) locate a line looking like

[INFO ][http ] [c7_64] bound_address {inet[/0:0:0:0:0:0:0:0:9201]}, publish_address {inet[/192.168.88.128:9201]}

You are interested in what's after publish_address. When accessing Sense use the IP:PORT you see there. In my example, the Sense URL would look like this:

http://192.168.88.128:9201/_plugin/marvel/sense/index.html

The CORS part is mostly valid for the scenario where Marvel is installed in a separate cluster and it shouldn't be needed when Marvel is installed in the same cluster as the monitored nodes. It's also needed when Shield is installed in the cluster.