Logging Best Practices: An Engineer's Checklist
honeycomb.io
honeycomb.io
The main exception I can think of is legacy systems that can't really be retrofitted with tracing. In which case you're probably not in a position to implement logging best practices either. I suppose audit is another exception, where you want a longer-term record of what's happened, but even there I think traces get you the much better story of what happened across your environment and you just need a better archival storage solution for them.
Most platforms/languages have logging built in, and it's perfectly possible to emit OTel-compatible log messages (like the linked article recommends) and collect them using some agent like Prometheus.
In general, logging is definitely easier and more ubiquitous, but there are a lot more "best practices" that you have to enforce vs simply having been built into the APIs like they've been with distributed tracing.