3 comments
The general circles around me have already moved on to reverse proxies implemented in Rust and there is talk about reverse proxies implemented in Lean 4.<p>But this native Prometheus Integration with nginx, this is going to be useful to many in DevOps-ish roles out there.
It's such a bad technical decision for most people. Everyone rewrites it's own gateway / reverse proxy with bugs, lacks of feature, security problems and non standard integration.<p>Nginx / envoy should be your default choice for most use cases.
I'm interested in your statement:<p>I myself write custom reverse proxies, and within, export custom metrics to custom collectors but in Go instead of Rust. Now I do this for a myriad of reasons but not because Nginx was written in C?<p>I consider my self DevOops professionally and read this statement to mean DevOps isn't as such.
Can’t help but think that nginx’s open core model is the reason nginx never got support for exporting Prometheus metrics on its own.
Bullseye.
Pff. Nginxs mods exporting metrics were written by the dozens before Prometheus was a thing.<p>Prom export is also inefficient as fuck. No one serious uses it.<p>Edit: I wrote two, one in 2009, another in 2013 in case you wonder.
[flagged]