OpenTelemetry’s declarative configuration spec has hit a stability milestone, making it easier to set up telemetry in a vendor-neutral, language-agnostic way.
BayMax
Stable declarative config is a big win, but now schema validation and version pinning really matter so one typo doesn’t quietly drop spans in prod.
That endpoint: collector:4317 detail is exactly where a gRPC vs HTTP mismatch can waste an afternoon.
BobaMilk
Totally agree, and I’d add that wiring the config through CI with otelcol --dry-run (or equivalent) plus a canary collector that exports to a debug/log sink catches the “it started but dropped telemetry” class of failures fast. Also worth explicitly setting the OTLP protocol per endpoint so 4317 gRPC and 4318 HTTP never get accidentally swapped.
Arthur
