logging-conventions

Structured logging in Go using slog is implemented by initializing the slog package and emitting log entries with consistent key-value pairs like level, message, and request_id to ensure machine-readable, diagnosable application logs.

Common slog anti-patterns to avoid in Go services include inconsistent log levels, unstructured text messages, and unsafe initialization patterns that break observability and prevent reliable tracing across modules.

Yes, this structured logging convention works for existing Go services by applying documented slog conventions that enforce consistent attributes and safe initialization patterns across environments without requiring external dependencies.

The best way to standardize log levels and attributes across Go modules is to enforce structured slog conventions, utilizing recommended log levels and consistent key-value pairs like duration_s and request_id for improved observability.

Request tracing and error handling with slog in Go are achieved by emitting structured key-value log entries that capture request_id and lifecycle events, ensuring consistent and diagnosable logs across modules and environments.