The idea is interesting, I wouldn't throw away level based logging but this could complete it nicely.

Observability is indeed not necessarily easy to fit into a code base. Here is a potential approach to make it easier. I wouldn't use it on a project where we're only logging, but once you add metrics to the mix, this kind of probes can be worthwhile.

Looks like a nice tool. Should complete nicely my trusty lnav for unsupported formats.

Interesting little tool, can come in handy.

Interesting take... Is it really practical? Until which size is it viable? What are we loosing by aggregating? Also makes me wonder about alert fatigue... It clearly raises extra questions.

Excellent article about best practices for logging errors, most of it applies for other type of logs though.

Nice set of simple rules to improve the quality of your logs.

This is actually a good list. Clearly doesn't try to invalidate YAGNI at all, focuses more on this infrastructure things you need on most projects anyway either for debug purpose or because they allow you to change the system easily later which in fact... supports YAGNI.

Very sensible and simple advises on how to do logging in your application. Just lacks a bit a discussion on how to use the different log levels.

Interesting article about tracing, especially on the client side and how to correlate it with the server side tracing.