[Manjuuu]

> Often log lines will include a request ID.

Yes, always include a request id in every request structure you create and include it also in the response and print it. It would seem something obvious that everyone does by default but instead, no, it's not so obvious it seems.

[janci]

Not so obvious. How to implement it without passing request id to all the functions, when they are unrelated to request/http ? Especially in languages without thread-locals such as javascript?

[gh123man]

Many frameworks solve this with logger context. Add the properties you want to the logging context and all future logs in that context will have that property.

One simple example - Serilog enrichment https://github.com/serilog/serilog/wiki/Enrichment

This does however assume your entire application uses the same logger. But this is generally a requirement in services that require tracing like this.

[mrloba]

Nodejs now has async local storage built in, which makes this fairly easy.

[veyh]

For example: https://github.com/puzpuzpuz/cls-rtracer

[yakshaving_jgt]

You can stick it in a middleware which wraps the request lifecycle.