Stop Deploying Broken OTel Configs: Validate & Test Before You Ship
· 10 min read
OpenTelemetry Collector configurations are YAML files. There's no
schema, no type system, and no IDE that will tell you that
tail_smapling isn't a real processor. You find out when your pipeline
goes dark and someone starts paging the on-call.
The collector ships with otelcol validate, which catches syntax errors
and fails on unknown component types. That covers a slice of the
problem. It won't tell you that your send_batch_max_size is smaller
than your send_batch_size, that your memory limiter is effectively
disabled, or that you've hardcoded an API key in plain text.
