4 ms·
Not sure I follow that logic? If you have a heavily used service, it's likely to have many concurrent requests logging into the same log stream and you absolut
by NovemberWhiskey 5y ago
Not sure I follow that logic?
If you have a heavily used service, it's likely to have many concurrent requests logging into the same log stream and you absolutely need a request correlation identifier to be able to thread the log statements for a single request back together.
That's essential even if you don't actually call any other services as part of your implementation.
- hinkley 5y agoCorrelationIDs aren’t just good for hard failures. They’re also good for figuring out why your backend started getting 20% more traffic on Monday for no reason. Someone introduced a duplicate call somewhere. But where?
- kerblang 5y agoLate reply: This scenario is reasonable and I usually handle it by logging the thread ID in multi-threaded systems, which amounts to a "free" global variable.