When incidents are active, traces usually tell you that something is wrong. The harder problem is figuring out who is affected and why, quickly.
OpenTelemetry eBPF Instrumentation (OBI) v0.7.0 adds HTTP header enrichment so spans can carry request context like tenant or user segment. That context is often exactly what helps you move from “error rate is up” to “this is isolated to one customer cohort”.
The best part: this is a config change on OBI itself. You do not need to rebuild or redeploy your existing applications.

OpenTelemetry's platform is an observability framework, offering insights into distributed tracing, metrics collection, and log management for cloud-native applications. Through documentation, tutorials, and community contributions, OpenTelemetry provides insights into instrumenting applications to monitor performance and troubleshoot issues. Developers and DevOps teams can learn about distributed tracing standards, telemetry data formats, and integration with observability tools to gain visibility into complex distributed systems.

OpenTelemetry

OpenTelemetry eBPF Instrumentation (OBI) v0.7.0 introduces HTTP header enrichment for spans, allowing request context like tenant ID or user segment to be captured and surfaced during incident triage. The feature is configured entirely within OBI — no application code changes or redeployment needed. A policy-based config controls which headers are included, excluded, or obfuscated (e.g., masking authorization tokens while exposing x-tenant-id). This lets teams filter traces by enriched attributes to quickly isolate which customer cohort is affected during an incident.

OBI Gives Incident Response the Request Context It Needs