OTel Collector Drift Lint

It reads an OpenTelemetry Collector config as YAML and applies 39 rules. Eight of them name components the Collector no longer accepts, such as the jaeger exporter removed in contrib v0.107.0 and the memory_ballast extension removed in v0.113.0. Twenty-nine name attributes the semantic conventions renamed, like http.method to http.request.method. Every finding carries a line number and the replacement.

Platform and SRE engineers who own the Collector config for a team: the gateway deployment, the daemonset agent, the sidecar in a service chart. If you are the person who bumps the Collector image tag and watches whether the pod comes back, and whether the dashboards keep drawing afterwards, this is aimed at you.

A YAML linter checks that the document parses. Every finding here is valid YAML. The jaeger exporter block is well formed; the Collector simply refuses to start because that component no longer exists. A filter keyed on http.target parses perfectly and quietly matches nothing once the SDK emits url.path instead.

Linting the file you have open is free and complete: every rule runs, every finding shows its line and its replacement, with no watermark, no trial limit and nothing held back. The licence key adds scope and ownership: one command that sweeps every YAML in the workspace, a JSON or Markdown report you keep, and a non-zero exit for CI.

A freelance SRE or observability contractor bills roughly $100 to $150 an hour, and reading one gateway config against the Collector changelog and the semantic convention history takes most of an hour, per config. The 82-line sample config in this repository carries 25 findings across 20 errors and 5 warnings.