The training doesn't even mention going back to add the prometheus service to the Services Vagrant box so I could have missed something but I don't think so.
Ive run vagrant up in the correct folder, it is adding prometheus to the Services box, I can curl to 192.168.33.10:9090/status and 192.168.33.10:3000 from inside the VM but cannot reach it from my local machine.
I can reach the Kibana endpoint at 5601 and all the services we need that were introduced prior to the Monitoring chapter.
This is the line in the Vagrantfile that I assume is trying to expose the ports:
inline: "docker run -d -p 9090:9090 -v /home/vagrant/prometheus.yml:/etc/prometheus/prometheus.yml prom/prometheus:0.16.0rc1"
Results of portscan
Open TCP Port: 22 ssh
Open TCP Port: 111 sunrpc
Open TCP Port: 2375
Open TCP Port: 5601 esmagent
Open TCP Port: 8080 http-alt
Open TCP Port: 8300 tmi
Open TCP Port: 8301 amberon
Open TCP Port: 8302
Open TCP Port: 8400 cvd
Open TCP Port: 8500 fmtp
Open TCP Port: 9200 wap-wsp
Open TCP Port: 9300 vrace
Open TCP Port: 37401
Help get this topic noticed by sharing it on Twitter, Facebook, or email.
Hi - Rick (the author) here. I just downloaded the 0410 Vagrantfile and started it up. Unfortunately, I cannot reproduce the problem.
The docker command that starts up prometheus should map the container port 9090 to the host (192.168.33.10). I wonder if it could be something with the networking on your machine.
The only idea I can think of off the top of my head is to change the first port in the -p option passed to Docker. This will change the port for the dashboard on the vagrant box. For example:
inline: "docker run -d -p 9999:9090 -v /home/vagrant/prometheus.yml:/etc/prometheus/prometheus.yml prom/prometheus:0.16.0rc1"
This will make it available on 9999. Just a shot in the dark. Maybe there's something with that port on your machine.
Apologies for the trouble.
see the change log