Fork: github.com/rubyjedi/postman-prometheus
Upstream: postman-prometheus
The original postman-prometheus tool was useful: run a Postman collection, export the results as Prometheus metrics. One shot, one collection.
What I needed was: run several collections, continuously, all feeding into one /metrics endpoint. The idea being that your Postman collections — which already describe your API contracts — double as live health checks you can scrape with Prometheus and visualize in Grafana.
What I Added#
- Multiple collections in parallel — each one configured independently, running on its own continuous loop
- Per-collection metric namespacing — so results from different collections don’t collide in Prometheus
- Single
/metricsendpoint — Prometheus scrapes one place, gets everything
Why It Exists#
I had several independent API surfaces to monitor across different teams. Running a separate exporter instance per collection would have been fine but messier to operate. One process, one scrape target, unified Grafana dashboard — much cleaner.
Status#
Active. Still runs in production monitoring setups where I’ve deployed it.
More details on this project in my professional portfolio at rubyjedi.com.