Thanks, that helped! I think the piece I was missing is using the same port for metrics that my app is using. Also, I may have missed it, but now I can hit https://myapp.com/metrics from my browser and can see the output. Is there a way to protect that publicly, or only make it available internally?
sorry, or did you mean how to do it in PromEx? Because the blog post talks about Peep, which is the library that exposes your Prometheus metrics. The post gives an option for how to run a second bandit server that hosts the metrics on port 9091, which your app doesn't expose publicly by default
Thanks - yeah, mostly looking how to do this with PromEx and Fly. I'm not sure how to protect that endpoint but still allow Fly to scrape it internally.
Comments