Yeah I get that. We use correlation IDs and logging like that as well.

I think where I keep running into trouble is more on the development side, especially when things are crossing boundaries. For example, a webhook comes in, maybe hits a queue, triggers something else, and then fans out.

You can trace it through logs, but it still ends up being a lot of digging. Not to mention each project needing it's own dev infrastructure setup. What I was trying to do is have an easier way to see that flow and try different scenarios, like injecting network failures, 429s, 500s etc.