opentelemetry-ebpf-instrumentation This Week: HTTP Metric Cleanup, DB Sanitization and New Tracer Options
opentelemetry-ebpf-instrumentation (OBI) instruments running services with eBPF, no code changes needed. The maintainers landed 45 commits this week, and the headline change is a metric hygiene fix: empty http.route and url.template attributes no longer pollute HTTP metrics. Here is what else moved.
HTTP metrics get cleaner
The most user visible change this week is #4264. OBI used to add empty http.route and url.template attributes to HTTP metrics. Empty attribute keys still count against cardinality in a backend, and they carry zero information. Now the metrics skip empty values, which keeps your metric stream lean.
Related, a fix in the generictracer addressed missing HTTP methods on spans for apps captured through the generic tracer, and another commit added the HTTP protocol version as a metric attribute. If you chart HTTP/1 vs HTTP/2 latency, that dimension is now available.
The maintainers also documented the HTTP duration dimension deprecations in the telemetry schema this week, via PR #4159. If you rely on older duration dimensions, read that doc before upgrading.
Database sanitization moves up a level
PR #4262 reworked how query sanitization works. Instead of handling sanitization per database backend, it moved to a DB wide level, and Redis now gets sanitized too. Redis raw queries appearing in spans was a real leak of request data. After the change, Redis commands get the same redaction treatment as SQL queries.
The go-sqllexer module also jumped to v0.2.6 in the dependency update, which affects SQL sanitization quality as well.
New tracer and connectivity options
Operators get a few new knobs this week:
- An option to disable Go channel span-link probes. Span-links on Go channel sends can be noisy; large Go apps can now turn the probes off instead of living with the extra links.
- Optional TLS and mutual TLS on the k8s-cache connection, merged earlier in the window. Useful if the cache runs across a trust boundary.
- OBI now stops header context propagation on services that already export native OTel traces, avoiding duplicate propagation work on mixed fleets.
The security relevant change is the bump of go.opentelemetry.io/otel/trace and otel/sdk to v1.47.0, marked [SECURITY] in the trace module update. If you build from source, refresh your builds to pick this up.
Small fixes users actually hit
- The Gunicorn relative chdir fix makes Python route discovery work when Gunicorn starts with a relative working directory.
- A JVM memory metrics fix covers HotSpot builds without USDT probes, so runtime metrics no longer come back empty on stripped JVMs.
- The netolly shutdown fix releases sockets, BPF objects and goroutines when OBI stops. Fewer leaked resources on restart loops.
CI got love too: a series of integration test speedups landed, and the devdocs/config/version-2.0 files including the config v2 migration docs saw heavy edits. The v2 config format is clearly the focus right now.
What to watch
- The HTTP duration dimension deprecations in the telemetry schema. Migrate dashboards before your next upgrade.
- The v2 config format and
migration-v2.yamltest data keep changing. If you migrate configs, pin to a tested release. - The Redis sanitization change can alter span contents. Alert rules that match on raw Redis commands may need updating.
Read the full history on the project repository.