Ask Bjørn Hansen 82e7f4398b fix(logger): render full logfmt line as journal MESSAGE
The native journal handler only put the bare msg string in MESSAGE,
so default `journalctl` output lost all slog attributes (env, name,
ip_version, etc.) that were visible with the old TextHandler path.

Wrap the slog-journal handler so each record's MESSAGE is rendered
through slog.TextHandler — producing the same `level=INFO msg="..."
key=val` format as before — while still emitting every attribute as
a structured journal field for `journalctl -o verbose` / field-based
filtering.

Also fix go.mod: slog-journal is a direct dependency.
2026-04-19 02:06:29 -07:00
2025-06-06 19:50:30 -07:00
2025-06-06 19:08:16 -07:00
2025-09-21 12:10:05 -07:00
2024-01-20 11:48:32 -07:00
2025-06-06 19:56:43 -07:00

Common library for the NTP Pool project with shared infrastructure components.

Packages

  • apitls - TLS setup for NTP Pool internal services with embedded CA
  • config - NTP Pool project configuration with environment variables
  • ekko - Enhanced Echo web framework with observability middleware
  • health - Standalone health check HTTP server
  • kafka - Kafka client wrapper with TLS support
  • logger - Structured logging with OpenTelemetry integration
  • metricsserver - Prometheus metrics HTTP server
  • timeutil - JSON-serializable duration types
  • tracing - OpenTelemetry distributed tracing setup
  • types - Shared data structures for NTP Pool
  • ulid - Thread-safe ULID generation
  • version - Build metadata and version information
  • xff/fastlyxff - Fastly CDN IP range management

Go Reference

Description
No description provided
Readme BSD-3-Clause 329 KiB
Languages
Go 99.3%
Shell 0.6%