This is a typical over-architecting issue you describe. - All the programs I work on are running on the JVM so I know how the trace looks like and how it is im

This is a typical over-architecting issue you describe. - All the programs I work on are running on the JVM so I know how the trace looks like and how it is implemented so it is not leaky nor brittle -Tracing back what caused what is a pain if you don't see the full trace. - The indirection caused by an eventbus message passing a microservice boundary makes it practically impossible to debug - passing on the trace will let you know __immediately__ where the problem is I'm not a purist, I'm a pragmatist. I don't care if a solution is not pure if it works, spares my time, and most importantly: does not come with a burden. This tracing can be put behind a feature toggle, or an aspect/decorator/whatever. You might call this a hack, but it lets me ship, maintain and support software while others still stand at the whiteboard planning.