I just had a 1h call with @akoutmos.bsky.social about it and I love it, but I wanted to explore the "low level" parts (Peep + Tracking custom Telemetry Events) before reaching for a fully fledged solution like PromEx. But I'll get there eventually!
Comments
Log in with your Bluesky account to leave a comment
Like Peter said. PromEx builds upon these tools and offers turn key metrics collection and Grafana dashboards for libraries such as Phoenix, Liveview, Oban, Absinthe, etc (https://hexdocs.pm/prom_ex/readme.html#available-plugins).
If you want to just experiment with Telemetry it's probably more than you need.
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
Comments
If you want to just experiment with Telemetry it's probably more than you need.