ration/pkg/telemetry/logging.go
caelum0x 13abc31645 feat(ration): observability, infra-as-code, security hardening, and test depth
Phase 2 sections 2-6 and 8 of docs/SCALE-EXPANSION.md:

- pkg/telemetry + pkg/metrics: OpenTelemetry trace propagation and
  Prometheus metrics across every service hop (CLI -> agent -> gateway ->
  card-issuance/tenant-registry/auth -> ledger-core), tracing added to
  ledger-core itself via services/ledger-core/src/telemetry.rs.
- infra/: otel-collector + Prometheus + Grafana docker-compose stack, a
  Terraform ECS Fargate module + dev/staging/prod envs (plan-only, no
  apply — real AWS spend is an owner action), and a dev-only mTLS CA
  (infra/dev-ca) wired through pkg/mtls + services/ledger-core/src/mtls.rs.
- services/audit-log (from the prior commit) gets its async mirror writer
  in services/ledger-core/src/audit_mirror.rs, and services/gateway gets
  a per-tenant token-bucket rate limiter (internal/ratelimit).
- Test depth: a Rust proptest suite proving concurrent ApplyEntry never
  breaches the reserve floor (tests/apply_entry_proptest.rs, passing), a Go
  fuzz seed corpus for the policy envelope (rules_fuzz_test.go), a libFuzzer
  harness for the C WAL frame parser (services/wal/fuzz, deliberately not
  wired into `make test` per its own Makefile comment - needs a
  libFuzzer-bundled clang), and a real chaos test
  (scripts/chaos/kill-ledger-mid-write.sh) that SIGKILLs ledger-core
  mid-write under concurrent load and verifies via ListEntries that
  nothing was lost or double-applied.
- docs/formal/ledger.tla: a TLA+ spec of the ledger state machine (balance
  >= reserve_floor safety, HOLD-eventually-resolves liveness) plus a TLC
  model config - not run through TLC in this pass, that's a precise
  documented TODO, not faked.
- docs/adr/0001-0004, docs/RUNBOOK.md, docs/SLO.md, docs/THREAT-MODEL.md.

Verified: `make build && make test` clean (C WAL, Rust incl. the new
proptest suite, all 10 Go modules) from a cold target.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
2026-10-19 12:25:58 +03:00

46 lines
1.6 KiB
Go

package telemetry
import (
"context"
"log/slog"
"os"
"go.opentelemetry.io/otel/trace"
)
// NewLogger returns a structured JSON slog.Logger (log/slog per
// docs/SCALE-EXPANSION.md section 2) tagged with serviceName, writing to
// stdout. Every service's main.go should construct its base logger with
// this (replacing a bare slog.NewJSONHandler call) so every log line
// everywhere carries the same "service" field to filter by in whatever
// aggregates stdout (docker-compose logs, CloudWatch, etc).
func NewLogger(serviceName string) *slog.Logger {
handler := slog.NewJSONHandler(os.Stdout, &slog.HandlerOptions{
AddSource: true,
})
return slog.New(handler).With(slog.String("service", serviceName))
}
// LogAttrs returns the correlation_id, trace_id and span_id attributes
// carried by ctx, suitable for splatting into any slog call:
//
// logger.LogAttrs(ctx, slog.LevelInfo, "handled request", telemetry.LogAttrs(ctx)...)
//
// trace_id/span_id are read from the active OpenTelemetry span in ctx
// (set by the otelgrpc stats handlers from grpc.go, or by WithSpan), so
// a log line can always be pivoted into the matching trace in
// Grafana/Tempo/Jaeger even without an explicit correlation ID.
func LogAttrs(ctx context.Context) []slog.Attr {
attrs := make([]slog.Attr, 0, 3)
if id := CorrelationIDFromContext(ctx); id != "" {
attrs = append(attrs, slog.String("correlation_id", id))
}
if sc := trace.SpanContextFromContext(ctx); sc.IsValid() {
attrs = append(attrs,
slog.String("trace_id", sc.TraceID().String()),
slog.String("span_id", sc.SpanID().String()),
)
}
return attrs
}