The worst time to discover that your services log differently is during an incident. It happens easily: each service is set up by a different person at a different time, so you end up with different field names, trace IDs in some services but not others, and a correlation ID that stops at the first hop. In a platform with several services I've worked on, the answer was a shared module for logging, auth and tracing; this starter is that idea rebuilt in the open.

The fix isn't a wiki page of conventions. It's making the right setup the default by putting it in a dependency.…