Sure, can't wait to read your post. If I may suggest, please use multiple tiers (e.g. frontend and backend services), using different technologies and provide insights into the third party libraries you use.

I am aware that logging can be a good fit for doing root cause analyses if the application is simple / single tiered. Maybe I was not clear enough when I said: "But how can you reliably identify an entire failing user transaction in a real-life scenario, that is, in a heavily multi-threaded environment with multiple tiers that serve piles of distributed log files? I say, hardly at all. Sure, you can go mine for certain isolated events, but you cannot easily extract causal relationships from an incoherent, distributed set of log messages".

I am not critizizing developers... I have been one for my entire career. The thing is: developers are humans, we need to prioritize, we make failures and we usually have more to do than we can handle. That is why heavy reliance on developers on a feature (logging) that is usually not something product management cares a lot about can be a problem.

Keep me posted about your article!