[hnwizard]

nginx has been a fantastic project ever since its launch with little real competition out there.

That said, I've been running it since the early days, on super heavy production loads and never felt the need to have some more "decent" metrics out of it. I assume you're referring to real time metrics here.

Most if not everything can be gathered from the logs, which nginx is very flexible with.

I fail to understand why some missing metrics in a great product make you think to migrate everything to Caddy?

[pachico]

Because I use as a gateway for fastcgi and as TLS initiator, mostly. Nginx doesn't allow you to have distinct metrics for both use cases, which is far from ideal.

My tests in controlled environments show that caddy is absolutely fine for my workload and has perks that make my life easier. Some have been mentioned in this thread already.

Metrics is a must have in our case as we have many things to manage, few people to maintain things and alerts are the only way to grow. For alerts you need metrics.

[pachico]

Regarding metrics from logs, you might agree that it's now an overkill.

[hnwizard]

I don't disagree, but there are always multiple solutions to problems we face, and the solution is not always simply to move on to the next product.

No product would ever cater to each and every need, and that's fine.

You have choice, if something doesn't satisfy you, you can sometimes fix the problem, improve the product or write your own module (when its opensource), or switch to another solution. Look at the opentelemetry comment below as another possibility to get what you want done.

There are so many choices today, and you enjoy the freedom of choice. If something else works better for you, use that other something.

There's no need to complain.