While I somehow understand Prometheus idea that pull is easier to scale than push I've had a bad luck with it. First of all Prometheus doesn't even consider mo

While I somehow understand Prometheus idea that pull is easier to scale than push I've had a bad luck with it. First of all Prometheus doesn't even consider monitoring of long-running jobs other than pull way (which didn't make sense for me). There is push gateway [0] but clients libraries seem to consider it only for short-lived jobs where you can send the metrics at the end [1]. It seems I couldn't "push" from long living jobs trivially Second when using it for example with django you have to be careful with how you handle multiprocessing that UWSGI/gunicorn does, see [2] - it has bitten me at leas once. Comparing to push model where I can just push metrics to [3] statsd_exporter directly and be done with it, but support for statsd is lacking both in terms of frameworks (everyone seems to be migrating to native clients...) and functionality (you've to do labeling basically manually [4]) To sum up: Prometheus is really great when it works, until you try to go off-track (intentionally or not, see django [2]) then you see its all undiscovered and immature landscape [0] https://github.com/prometheus/pushgateway https://github.com/prometheus/pushgateway [1] https://github.com/prometheus/client_python#exporting-to-a-pushgateway https://github.com/prometheus/client_python#exporting-to-a-p... [2] https://github.com/korfuri/django-prometheus/blob/master/documentation/exports.md#exporting-metrics-in-a-wsgi-application-with-multiple-processes-globally https://github.com/korfuri/django-prometheus/blob/master/doc... [3] https://github.com/prometheus/statsd_exporter https://github.com/prometheus/statsd_exporter [4] https://github.com/prometheus/statsd_exporter#glob-matching https://github.com/prometheus/statsd_exporter#glob-matching