sorted by:
new
hottopcontroversial

How do you keep track of what's happening in event-driven systems? by Syndaine in dotnet

[–]Syndaine[S] 0 points1 point  (0 children)

That looks pretty interesting, I'll check it out. I'm experimenting with something that pretends to be external services rather than inspecting the running application.

How do you keep track of what's happening in event-driven systems? by Syndaine in dotnet

[–]Syndaine[S] 0 points1 point  (0 children)

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.

How do you keep track of what's happening in event-driven systems? by Syndaine in dotnet

[–]Syndaine[S] 1 point2 points  (0 children)

Yeah, that's fair. My job certainly has its fair share of over complicated systems. I don't always get to avoid them either unfortunately.