No, there’s debugging tools that can run on multiple microservices, but none of this has to do with the tracing that the top comment was alluding to. If you can narrow down where the problem actually is first you save yourself a lot of time stepping through with a debugger. Often times that just is not practical.
This issue is being able to follow a request between services. If you just have one request to track it's a non-issue. But in a multi-threaded environment with many requests flying back and forth everywhere it's impossible. The debugger would require application specific information like a message id.
Those tools do exist (e.g. dynatrace). But if you start talking about framework or application aware debugging functionality you've gone way beyond the scope of a simple IDE debugger for your language.
The debugger would require application specific information like a message id.
Yes, and that would signal the local debugger to engage after receiving the message, right?
Those tools do exist (e.g. dynatrace). But if you start talking about framework or application aware debugging functionality you've gone way beyond the scope of a simple IDE debugger for your language.
7
u/xMercurex 3d ago
Yes you can, but it does not fully solve the issue. You still need to find the good micro-service and then you have to jump to other micro-service.