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>
40 lines
1.4 KiB
Go
40 lines
1.4 KiB
Go
package telemetry
|
|
|
|
import (
|
|
"context"
|
|
|
|
"github.com/google/uuid"
|
|
)
|
|
|
|
// CorrelationIDHeader is the gRPC metadata key a correlation ID travels
|
|
// under between Ration services. Unlike a trace ID (which identifies a
|
|
// span tree inside the tracing backend), the correlation ID is a plain
|
|
// string every service's structured logs also carry, so "find every log
|
|
// line for this one CLI invocation" works with a simple grep even
|
|
// without a tracing backend running.
|
|
const CorrelationIDHeader = "x-ration-correlation-id"
|
|
|
|
type correlationIDKey struct{}
|
|
|
|
// NewCorrelationID generates a fresh correlation ID. Called once per
|
|
// externally-triggered unit of work: a CLI command invocation, an
|
|
// incoming webhook, or one agent loop tick — everything that unit of
|
|
// work causes downstream reuses the same ID.
|
|
func NewCorrelationID() string {
|
|
return uuid.NewString()
|
|
}
|
|
|
|
// ContextWithCorrelationID returns a copy of ctx carrying id, retrievable
|
|
// later via CorrelationIDFromContext.
|
|
func ContextWithCorrelationID(ctx context.Context, id string) context.Context {
|
|
return context.WithValue(ctx, correlationIDKey{}, id)
|
|
}
|
|
|
|
// CorrelationIDFromContext returns the correlation ID stored in ctx, or
|
|
// "" if none was ever set (e.g. a context never threaded through the
|
|
// client/server interceptors below).
|
|
func CorrelationIDFromContext(ctx context.Context) string {
|
|
id, _ := ctx.Value(correlationIDKey{}).(string)
|
|
return id
|
|
}
|