Merge remote-tracking branch 'origin/main' into otelbot/semconv-integration-v1.40.0-dev

Author: otelbot[bot]

.cspell/pl-words.txt

@@ -0,0 +1,188 @@
+agentów
+Agenty
+aplikacje
+aplikacji
+Automatyczna
+automatycznej
+Automatycznie
+backendu
+Bagaż
+bibliotek
+bramę
+branży
+całą
+chmurach
+chmurowego
+chmurowych
+czasie
+czasu
+czerpie
+długoterminową
+dokumentacji
+Dostarcza
+dostawców
+dostawcy
+doświadczenia
+Dowiedz
+dowolnego
+dużą
+Działa
+dzięki
+Ekosystem
+eksportowania
+Eksportuj
+elastycznością
+filtruj
+frameworków
+Funkcje
+gdzie
+głównych
+gotowe
+granicami
+hybrydowych
+infrastrukturze
+inkubacji
+instrumentacja
+instrumentacji
+Instrumentuj
+Integracje
+interfejsów
+Interfejsy
+jako
+jednolity
+języka
+językach
+Języki
+języków
+kieruj
+kilka
+klasie
+kodu
+kolektora
+kolektorów
+komercyjnych
+komponentach
+komponentami
+Komponenty
+kontekst
+kontekstem
+kontekstowe
+kontekstu
+koreluj
+Korzystaj
+korzystając
+korzystające
+który
+liderów
+logi
+łącząc
+Metadane
+metryk
+metryki
+między
+modyfikowania
+najlepsze
+napędzany
+Natywne
+niezależna
+niezależne
+niezależnych
+obserwowalności
+odbierania
+oprogramowania
+organizacje
+organizacji
+Otwarte
+otwartoźródłowe
+otwartoźródłowy
+Otwarty
+otwartych
+pełną
+pełny
+połączenia
+Pomiary
+pomocą
+pomysły
+ponad
+popularnych
+Potok
+potrzebujesz
+Powstał
+Poznaj
+praktyki
+preferowanego
+produkcji
+projektem
+projektów
+Propagacja
+protokołu
+przechwytują
+przechwytywania
+Przegląd
+Przejrzyste
+Przenoś
+przepływa
+Przetwarzaj
+przetwarzania
+przez
+ramach
+Rekordy
+rozproszone
+Rozproszony
+rozproszonych
+rozwiązania
+rozwój
+sieciowego
+skalę
+specyfikacjach
+specyfikacje
+społeczności
+społeczność
+stabilne
+stabilność
+swojej
+swój
+sygnały
+Szukaj
+ścieżkę
+śladów
+ślady
+śledzenia
+środowiskach
+telemetryczne
+Twojej
+Tysiące
+Ujednolicone
+ujednolicony
+usług
+usługach
+uzależnieniem
+Uzyskaj
+używa
+Wdrażaj
+widok
+wieloletniego
+wielu
+więcej
+własnego
+własnej
+Wsparcie
+wsparciem
+Wspierane
+współdzielonym
+wszędzie
+wszystkich
+Wypróbuj
+zachowania
+Zacznij
+zapewnia
+zapytania
+zapytań
+zarządzanie
+Zaufany
+Zbudowane
+zerowym
+zestaw
+Zmieniaj
+znacznikiem
+źródłowego

.gitmodules

@@ -3,7 +3,7 @@
 	path = themes/docsy
 	url = https://github.com/google/docsy.git
   # cSpell:disable-next-line
-	docsy-pin = v0.14.3-37-g6b1698a3
+	docsy-pin = v0.14.3-44-gc6834296
 	docsy-note = "2024-04-01 Switching to google/docsy.git from cncf/docsy.git since we don't have any CNCF customizations."
 	docsy-reminder = "Ensure that any tag referenced by `docsy-pin` is present in the remote repo (url), otherwise add (push) the tags to the repo."
 [submodule "content-modules/opentelemetry-specification"]

config/_default/hugo.yaml

@@ -1,4 +1,4 @@
-# cSpell:ignore bluesky cicd docsy goldmark linkify netlify wordmark noopener
+# cSpell:ignore bluesky cicd docsy goldmark linkify netlify wordmark noopener llms
 baseURL: https://opentelemetry.io
 title: OpenTelemetry
 disableKinds: [taxonomy]
@@ -109,8 +109,8 @@ cascade:
 
   # Enable redirects for site root (and not locales)
   - outputs:
-      # This must match the equivalent of [outputs.home, redirects]
-      [HTML, markdown, RSS, redirects]
+      # This must match the equivalent of [outputs.home, LLMS, redirects]
+      [HTML, markdown, RSS, LLMS, redirects]
     target:
       kind: home
       sites: { matrix: { languages: [en] } }

content/en/blog/2026/obi-http-header-enrichment/index.md

@@ -0,0 +1,124 @@
+---
+title: OBI Gives Incident Response the Request Context It Needs
+linkTitle: OBI Incident Response Context
+date: 2026-04-10
+author: >-
+  [Tyler Yahn](https://github.com/MrAlias) (Splunk), [Nimrod
+  Avni](https://github.com/NimrodAvni78) (Coralogix)
+sig: SIG eBPF Instrumentation
+cSpell:ignore: Avni obfuscate x-tenant-id x-user-segment Yahn
+---
+
+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)](https://github.com/open-telemetry/opentelemetry-ebpf-instrumentation)
+[v0.7.0](https://github.com/open-telemetry/opentelemetry-ebpf-instrumentation/releases/tag/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.
+
+## Why this matters in practice
+
+Most teams have felt this pain: traces show latency and failures, but not enough
+request context to narrow scope during triage. Header enrichment closes that gap
+without requiring app code changes.
+
+For this demo, we include:
+
+- `x-tenant-id`
+- `x-user-segment`
+
+And we intentionally obfuscate:
+
+- `authorization`
+
+That gives responders useful debugging context while still masking sensitive
+values.
+
+## The config change
+
+This is the core policy used in the demo:
+
+```yaml
+ebpf:
+  # Needed so headers are captured for enrichment.
+  track_request_headers: true
+  payload_extraction:
+    http:
+      enrichment:
+        enabled: true
+        policy:
+          # Only emit headers that rules explicitly match.
+          default_action: exclude
+          # Replacement value for obfuscated headers.
+          obfuscation_string: '***'
+        rules:
+          - action: include
+            type: headers
+            scope: all
+            match:
+              patterns: ['x-tenant-id', 'x-user-segment']
+              case_sensitive: false
+          - action: obfuscate
+            type: headers
+            scope: all
+            match:
+              patterns: ['authorization']
+              case_sensitive: false
+```
+
+Two small details are worth calling out: `scope: all` applies rules to both
+request and response headers, and `case_sensitive: false` avoids missing headers
+because of casing differences.
+
+Turning this feature on or off is a simple OBI config update and OBI redeploy.
+No application rebuild required.
+
+## Visual walkthrough
+
+Baseline trace (before enrichment): no header attributes in the span.
+
+![Jaeger baseline trace with no enriched headers](v0-6-0-baseline.png)
+
+After enabling enrichment in OBI v0.7.0: the span now includes request header
+context.
+
+![Jaeger trace with enriched request header attributes](v0-7-0-header-enrichment.png)
+
+Note, now `authorization` is present but masked, while `x-tenant-id` and
+`x-user-segment` stay visible.
+
+![Jaeger span tags showing obfuscated authorization and included tenant and segment headers](v0-7-0-obfuscated-closeup.png)
+
+Traces can now be filtered by enriched attributes (for example
+`http.request.header.x-tenant-id`) to focus on the impacted cohort.
+
+![Jaeger trace search filtered by enriched header attribute for tenant triage](v0-7-0-triage.png)
+
+## Takeaway
+
+OBI
+[v0.7.0](https://github.com/open-telemetry/opentelemetry-ebpf-instrumentation/releases/tag/v0.7.0)
+header enrichment is a practical debugging feature: it improves incident
+response signal, keeps policy explicit, and can be rolled out (or rolled back)
+by changing OBI configuration only.
+
+Already running OBI? Upgrade to v0.7.0 and give
+[header enrichment](/docs/zero-code/obi/configure/metrics-traces-attributes/#http-header-enrichment-for-spans)
+a try.
+
+New to OBI? Start with the
+[demo used in this post](https://github.com/open-telemetry/opentelemetry-ebpf-instrumentation/tree/b1f159092a3743464e53e78b16f0c4d817c47e02/examples/http-header-enrichment-demo)
+to see an end-to-end example of how it works. Then be sure to check out how to
+[start using OBI](/docs/zero-code/obi/setup/) for your application.
+
+Have you already tried header enrichment? Let us know how it went. Find us on
+the
+[`#otel-ebpf-instrumentation` CNCF Slack channel](https://cloud-native.slack.com/archives/C06DQ7S2YEP),
+or
+[open a discussion](https://github.com/open-telemetry/opentelemetry-ebpf-instrumentation/discussions)
+if you have feedback that could help shape future releases.

content/en/blog/2026/obi-http-header-enrichment/v0-6-0-baseline.png

@@ -18,7 +18,7 @@ Helm's [documentation](https://helm.sh/docs/) to get started.
 - 6 GB of free RAM for the application
 - Helm 3.14+ (for Helm installation method only)
 
-## Install using Helm (recommended)
+## Install using Helm
 
 Add OpenTelemetry Helm repository:
 
@@ -46,13 +46,14 @@ helm install my-otel-demo open-telemetry/opentelemetry-demo
 > The OpenTelemetry Demo Helm chart version 0.11.0 or greater is required to
 > perform all usage methods mentioned below.
 
-## Install using kubectl
+### Use Helm to generate a Kubernetes manifests
 
-The following command will install the demo application to your Kubernetes
-cluster.
+The following command will generate a single Kubernetes manifest file which will
+contain a definition for all required resources. You can apply this manifest
+using `kubectl apply -f opentelemetry-demo.yaml` after generating it.
 
 ```shell
-kubectl create --namespace otel-demo -f https://raw.githubusercontent.com/open-telemetry/opentelemetry-demo/main/kubernetes/opentelemetry-demo.yaml
+helm template opentelemetry-demo open-telemetry/opentelemetry-demo --namespace otel-demo > opentelemetry-demo.yaml
 ```
 
 > [!NOTE]
@@ -61,11 +62,6 @@ kubectl create --namespace otel-demo -f https://raw.githubusercontent.com/open-t
 > one version to another. If you need to upgrade the demo, you must first delete
 > the existing resources and then install the new version.
 
-> [!NOTE]
->
-> These manifests are generated from the Helm chart and are provided for
-> convenience. It is recommended to use the Helm chart for installation.
-
 ## Use the Demo
 
 The demo application will need the services exposed outside of the Kubernetes