3 ms·
Better yet. Just use the trace id for the message. That id is correlated with all log statements already and it will allow you to in one go follow the whole flo
by spockz 1y ago
Better yet. Just use the trace id for the message. That id is correlated with all log statements already and it will allow you to in one go follow the whole flow of the user without setting up another per-request flow lookup table.
- RadiozRadioz 1y agoThe prerequisite to this is setting up OTEL tracing and having already instrumented everything. Which is not trivial. You can't "just use" it. It's like you get to the middle of a recipe and they say to "just" add in the meat you've already been marinating for 48 hours.
- Groxx 1y agoyou really only need it at the entry point to have a trace ID... but yeah. tracing is hard to add on later, though I'm glad it's becoming more common for newer code.
- spockz 1y agoTelemetry for me is table stakes. We have been doing forms of tracing (first home grown) since 2012. Strictly speaking only the edge gateway needs to know about it. Tracing is trivial to add with OTel. It is trivial with Spring Boot (since v3). At least on technical endpoint level. Adding tracing to business logic obviously requires work, but simple propagation is table stakes.