How do you find the actual root cause of a production bug?
Sometimes the hardest part of debugging isn't finding the error.
It's figuring out whether the error you're looking at is actually the *root cause*.
I've had cases where:
Service A fails → Service B throws an error → API returns 500
The obvious approach is to investigate Service B first.
But the real problem was actually somewhere earlier in the chain.
How do you guys approach these situations?
Do you start from the first error in the logs, use distributed tracing, inspect the execution flow manually, or have another method that works better?
Interested to hear how people handle this, especially in larger codebases.