What's new in LogLayer for Go

• See the main CHANGELOG.md for the auto-generated per-release log.

May 11, 2026

transports/newrelic:

Encoder updated to match the TypeScript transport format. Log entries now use timestamp, level, log, and attributes (nested) instead of the previous flat shape (logtype, loglevel, message, fields at root). Attribute validation added at encode time: maximum 255 attributes, 255-char names, 4,094-char string values.

May 10, 2026

transports/newrelic:

Initial release. New New Relic transport.

transports/betterstack:

Initial release. New Better Stack transport.

May 06, 2026

transports/axiom:

Initial release. New Axiom transport.

May 03, 2026

v2.1.0:

loglayer.Multiline(lines ...any) is a new value-wrapper that lets terminal transports preserve authored "\n" boundaries. The cli, pretty, and console transports collapse bare-string newlines to one line for security (log-forging, terminal-escape smuggling); the wrapper is a per-call developer-issued opt-in to that defense. Each authored line is still individually sanitized; only the boundaries between them are honored. JSON sinks and wrapper transports flatten via Stringer / MarshalJSON with no code change. See Multi-line messages.

The change also fixes a pre-existing bug in transport.JoinPrefixAndMessages where WithPrefix was silently dropped when Messages[0] was not a string. The prefix now folds in front of the %v-formatted first message.

A new Log Sanitization reference page covers what gets sanitized where, the threat model (log forging, terminal escape smuggling, Trojan Source), and the decision tree for transport authors.

transports/cli v2.2.0:

The cli transport now honors loglayer.Multiline values: authored multi-line content renders across rows on stdout / stderr while bare-string newlines are still stripped. Per-line sanitization for ANSI / CR / bidi / ZWSP is preserved within each authored line.

transports/cli v2.1.0:

New Config.TableColumnOrder []string knob pins the leading column order for slice-of-map metadata table rendering. Keys named here render in the listed order; the rest sort lexicographically and follow. Empty / nil keeps the previous fully-lexicographic behavior. See Pinning column order.

transports/pretty v2.1.0 and transports/console v2.1.0:

Same Multiline support as cli: authored multi-line content renders across rows; bare-string newlines still strip; per-line sanitization preserved.

transports/http v2.1.0:

New Config.String() redacts Headers values so an accidental log.Info(cfg) or fmt.Sprintf("%v", cfg) can't leak credentials passed via Authorization / X-API-Key / similar headers. Header keys stay visible for debuggability. Mirrors the redaction shape already used by transports/datadog.

defaultCheckRedirect now compares hosts case-insensitively, so legitimate same-host redirects with mixed-case URLs aren't refused. Cross-host refusal still applies; ports are still compared exactly.

New Config.ShutdownTimeout (default 5s) bounds how long Close waits for in-flight requests to finish during shutdown. When the timeout elapses, the worker's outbound HTTP requests are cancelled via context so Close can return even if the endpoint is wedged; previously a stuck endpoint could pin Close for up to the per-request Client.Timeout (30s default), and the parent flushTransports's 5s timeout would leak the close goroutine.

v2.0.1:

Republished every module with a clean go.mod. The v2.0.0 cascade shipped sub-module go.mod files containing dev-only replace directives and placeholder pseudo-version requires; downstream consumers saw go mod tidy 404 on the placeholders. No API changes; re-go get to pick up the cleaned modules.

May 02, 2026

v2.0.0:

Breaking: import paths bump to /v2. The loglayer core no longer mutates Messages[0] to fold the WithPrefix value into the message text. The prefix flows through TransportParams.Prefix and each transport decides how to render it. Built-in transports preserve v1 user-visible output via the new transport.JoinPrefixAndMessages helper; the cli transport opts into smart rendering (dim-grey user prefix separate from level color). See Migrating to v2 for the upgrade checklist.

loglayer:

Prefix is now exposed as a separate field on TransportParams and on every dispatch-time plugin hook param struct (BeforeDataOutParams, BeforeMessageOutParams, TransformLogLevelParams, ShouldSendParams). Transports and plugins can render or react to the prefix independently from the message string. The legacy "prepend prefix into Messages[0]" auto-mutation in v1.7.x stays in place for backwards compatibility within the v1 line; v2.0.0 removes it.

transports/cli:

Initial release. New CLI transport tuned for command-line app output: short level prefixes, stdout / stderr routing, TTY-detected ANSI color, no timestamps. Includes table rendering for slice-of-map metadata so the same call site emits a CLI table and a JSON array depending on the transport.

Apr 30, 2026

transports/gcplogging:

Initial release. New Google Cloud Logging transport.

transports/sentry:

Initial release. New Sentry transport.

loglayer:

MetadataFieldName is now a core Config knob. Set it once on loglayer.Config and metadata nests under the configured key uniformly across every transport, for both map and non-map values. Joins FieldsKey and ErrorFieldName as the third assembly-shape knob. See MetadataFieldName.

The resolved assembly shape (FieldsKey, MetadataFieldName, ErrorFieldName, SourceFieldName) is also published as loglayer.Schema on TransportParams and on the dispatch-time plugin hook param structs (BeforeDataOutParams, BeforeMessageOutParams, TransformLogLevelParams, ShouldSendParams). Plugins can navigate params.Data precisely without guessing keys.

The per-transport Config.MetadataFieldName field is removed from every wrapper (zerolog, zap, charmlog, phuslu, logrus, slog, otellog, sentry); set the core knob instead.

transports/pretty:

• Column-aligned YAML in expanded mode: same-level scalar keys pad to the longest sibling so values line up. Multi-line keys (nested maps, slices) don't participate in the alignment width.
• Nested rendering for keyed metadata: when Config.MetadataFieldName is set, the metadata value JSON-roundtrips into a nested map and renders as YAML under the configured key.

Apr 29, 2026

loglayer:

• Lazy evaluation: loglayer.Lazy(fn) defers value computation in WithFields until log dispatch time. The callback runs only when the level passes and re-evaluates on every emission, so expensive work costs nothing on filtered-out entries. See Lazy Evaluation.
• Groups in dispatch-time hooks: TransportParams.Groups and the four dispatch-time plugin hook param structs now carry the entry's merged WithGroup tags. Routing still happens before hooks fire; the slice is exposed so transports can ship groups in the wire payload and plugins can drive group-aware transformations. See Reading params.Groups.

transports/lumberjack:

Initial release. New rotating-file transport.

v1.1.0:

Multi-module split. Every transport (transports/*), plugin (plugins/*), and integration (integrations/*) now ships as its own independently-versioned Go module. Import paths are unchanged; you may need go mod tidy to pick up the new sub-module entries. Future breaking changes in any sub-package bump only that module's tag namespace, leaving go.loglayer.dev itself stable on v1. Full module list in monorel.toml.

fmtlog import path moved. The plugin moved from go.loglayer.dev/fmtlog to go.loglayer.dev/plugins/fmtlog for consistency with every other plugin. Update imports:

- import "go.loglayer.dev/fmtlog"
+ import "go.loglayer.dev/plugins/fmtlog"

Technically a SemVer-breaking change, but ships as a minor bump rather than v2.0.0 (the v1.0.x release went out with no known users yet).

v1.0.0:

Initial release. LogLayer for Go is a transport-agnostic structured logging facade: one fluent API on top of any logging library, JSON or pretty rendering, HTTP shipping, OpenTelemetry, or your own transport. Stable API; SemVer applies from this point forward. See Getting Started.