golang-samber-slog

Structure a slog-multi pipeline by composing sampling, formatting, and routing middleware with correct ordering before backend sinks. Use predicate-based routing semantics with Router or FirstMatch to ensure records reach intended destinations without being dropped or duplicated.

Sampling must come before formatting in a structured logging pipeline to prevent expensive formatting operations on records that will be dropped. This ordering ensures computational resources are not wasted processing log entries that the sampling middleware ultimately discards.

Scrub PII from Go slog records by integrating slog-formatter middleware in the pipeline before backend sinks. This ensures sensitive data like IP addresses and errors are cleaned into structured attributes prior to reaching downstream destinations such as Loki or Datadog.

Yes, you can use slog-gin middleware for HTTP request logging by configuring it to set WARN for 4xx responses and ERROR for 5xx responses. This integrates request-scoped attributes directly into the structured logging pipeline.

Router and FirstMatch are predicate-based routing semantics in slog-multi that control record distribution. Proper selection between them avoids dropped or duplicated records when directing logs to multiple backend sinks concurrently.