feat(telemetry): add headers, resources, and TLS for OTLP backends #7972
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Added support for: - Custom headers on OTLP exports (metrics, tracing, access logs) - Resource attributes on OTLP metrics and tracing sinks via the resources field - TLS telemetry gRPC backends Signed-off-by: Adrian Cole <[email protected]>
✅ Deploy Preview for cerulean-figolla-1f9435 ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #7972 +/- ##
==========================================
- Coverage 72.80% 72.79% -0.01%
==========================================
Files 237 237
Lines 35475 35495 +20
==========================================
+ Hits 25827 25839 +12
- Misses 7807 7811 +4
- Partials 1841 1845 +4 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
Contributor
Author
|
So I was able to get data to Elastic Cloud, but traces aren't rendering even though logs and metrics do.. index 167f76fd5..204dead9e 100644
--- a/examples/otel-headers/resources/gateway.yaml
+++ b/examples/otel-headers/resources/gateway.yaml
@@ -5,15 +5,10 @@ metadata:
spec:
endpoints:
- fqdn:
- hostname: localhost
- port: 4317
-# Use below for cloud OTLP endpoints
-# endpoints:
-# - fqdn:
-# hostname: otel.example.com
-# port: 443
-# tls:
-# wellKnownCACertificates: System
+ hostname: b7e5ce524b21440da7e3a9030fdf365d.ingest.us-central1.gcp.elastic.cloud
+ port: 443
+ tls:
+ wellKnownCACertificates: System
---
apiVersion: gateway.envoyproxy.io/v1alpha1
kind: EnvoyProxy
@@ -35,7 +30,7 @@ spec:
# Authorization header sent as gRPC initial metadata
headers:
- name: Authorization
- value: Bearer fake
+ value: ApiKey XXXXXXX==
resources:
service.name: envoy-gateway-example
service.version: v1.0.0
@@ -52,7 +47,7 @@ spec:
openTelemetry:
headers:
- name: Authorization
- value: Bearer fake
+ value: ApiKey XXXXXXX==
resources:
service.name: envoy-gateway-example
service.version: v1.0.0
@@ -84,7 +79,7 @@ spec:
# Authorization header sent as gRPC initial metadata
headers:
- name: Authorization
- value: Bearer fake
+ value: ApiKey XXXXXXX==
---
apiVersion: gateway.networking.k8s.io/v1
kind: GatewayClass
cc @anuraaga @axw if any ideas and I can take the config thing offline as I think it is a different PR whatever that is.. |
|
@codefromthecrypt can you see any docs in |
Contributor
Author
|
@axw so it wasn't selected by default so I added it.. 
here's one {
"_index": ".ds-traces-generic.otel-default-2026.01.07-000005",
"_id": "AZvFiCdw3JeNWXAgrBz-",
"_version": 1,
"_score": null,
"fields": {
"resource.attributes.telemetry.sdk.name.text": [
"envoy"
],
"scope.name": [
"envoy"
],
"resource.attributes.telemetry.sdk.name": [
"envoy"
],
"resource.attributes.agent.name.text": [
"envoy/cpp"
],
"upstream_address": [
"66.241.125.232:443"
],
"attributes.span.name": [
"router httproute/envoy-gateway-system/backend/rule/0 egress"
],
"attributes.event.success_count": [
1
],
"attributes.service.target.type": [
"http"
],
"attributes.timestamp.us": [
1768545582880064
],
"telemetry.sdk.language": [
"cpp"
],
"processor.event": [
"span"
],
"upstream_cluster": [
"httproute/envoy-gateway-system/backend/rule/0"
],
"attributes.upstream_cluster": [
"httproute/envoy-gateway-system/backend/rule/0"
],
"peer.address": [
"66.241.125.232:443"
],
"telemetry.sdk.version": [
"bad8280de85c25b147a90c1d9b8a8c67a13e7134/1.36.4/Modified/RELEASE/BoringSSL"
],
"deployment.environment": [
"production"
],
"event.outcome": [
"success"
],
"scope.attributes.service.framework.name": [
"envoy"
],
"parent_span_id": [
"9b6b7fb183615f61"
],
"attributes.response_flags": [
"-"
],
"span_id": [
"5f59db9765a0f256"
],
"kind": [
"Client"
],
"attributes.http.protocol": [
"HTTP/2"
],
"span.id": [
"5f59db9765a0f256"
],
"span.type": [
"external"
],
"timestamp.us": [
1768545582880064
],
"resource.attributes.telemetry.sdk.version": [
"bad8280de85c25b147a90c1d9b8a8c67a13e7134/1.36.4/Modified/RELEASE/BoringSSL"
],
"resource.attributes.deployment.environment": [
"production"
],
"attributes.upstream_address": [
"66.241.125.232:443"
],
"name": [
"router httproute/envoy-gateway-system/backend/rule/0 egress"
],
"parent.id": [
"9b6b7fb183615f61"
],
"resource.attributes.service.name.text": [
"envoy-gateway-example"
],
"attributes.span.name.text": [
"router httproute/envoy-gateway-system/backend/rule/0 egress"
],
"scope.attributes.service.framework.version": [
"bad8280de85c25b147a90c1d9b8a8c67a13e7134/1.36.4/Modified/RELEASE/BoringSSL"
],
"attributes.span.subtype": [
"http"
],
"resource.attributes.service.name": [
"envoy-gateway-example"
],
"span.representative_count": [
1
],
"upstream_cluster.name": [
"httproute/envoy-gateway-system/backend/rule/0"
],
"span.name": [
"router httproute/envoy-gateway-system/backend/rule/0 egress"
],
"resource.attributes.agent.version": [
"bad8280de85c25b147a90c1d9b8a8c67a13e7134/1.36.4/Modified/RELEASE/BoringSSL"
],
"resource.attributes.agent.name": [
"envoy/cpp"
],
"attributes.service.target.name": [
""
],
"resource.attributes.telemetry.sdk.language": [
"cpp"
],
"attributes.span.type": [
"external"
],
"attributes.component": [
"proxy"
],
"telemetry.sdk.name": [
"envoy"
],
"duration": [
256249000
],
"attributes.span.duration.us": [
256249
],
"trace.id": [
"ddd03f3cca6e589a2af1ed3897ecbf19"
],
"span.duration.us": [
256249
],
"event.success_count": [
1
],
"resource.attributes.service.version": [
"v1.0.0"
],
"attributes.upstream_cluster.name": [
"httproute/envoy-gateway-system/backend/rule/0"
],
"scope.attributes.service.framework.name.text": [
"envoy"
],
"attributes.upstream_cluster.name.text": [
"httproute/envoy-gateway-system/backend/rule/0"
],
"trace_id": [
"ddd03f3cca6e589a2af1ed3897ecbf19"
],
"attributes.service.target.name.text": [
""
],
"span.subtype": [
"http"
],
"http.protocol": [
"HTTP/2"
],
"response_flags": [
"-"
],
"http.status_code": [
"200"
],
"attributes.http.status_code": [
"200"
],
"attributes.processor.event": [
"span"
],
"component": [
"proxy"
],
"attributes.peer.address": [
"66.241.125.232:443"
],
"attributes.event.outcome": [
"success"
],
"scope.version": [
"bad8280de85c25b147a90c1d9b8a8c67a13e7134/1.36.4/Modified/RELEASE/BoringSSL"
],
"attributes.span.representative_count": [
1
],
"event.dataset": [
"generic.otel"
]
},
"sort": [
"2026-01-16T06:39:42.880Z",
9
]
} |
|
Thanks, so definitely seems to be an issue with the fields... Nothing obvious jumps out. If you're able to grab an OTLP dump (OTLP/JSON is fine if easier to drop here) then I can try to reproduce and see what's up (probably on Monday). |
Contributor
Author
|
Reviewers Nevermind the elastic cloud trace data glitch, as it isn't introduced in this PR. I'm glad we can now see glitches, but resolving them will be a PR or some change to my account. otel-tui shows this all works. Sorry about the distraction. Please review this change! @axw here's the trace data.. since it seems a glitch unrelated to this PR (though maybe to either envoy or envoy-gateway), please ping me and I'll try to figure a place to correct whatever it is, or if it is my cloud account lemme know. Details |
zirain
approved these changes
Jan 18, 2026
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What type of PR is this?
feat(telemetry): add new feature
What this PR does / why we need it:
Adds support for resource attributes on OTLP metrics and tracing sinks, enabling callers like Envoy AI Gateway to map all attributes required for Elastic Cloud OTLP endpoints.
This completes the
OTEL_RESOURCE_ATTRIBUTESequivalent for all three OTLP signals:resourcesfield (maps to Envoy'sresource_attributes)resourcesfield (maps to Envoy'sresource_detectorswithStaticConfigResourceDetector)resourcesfield (maps to Envoy'sresource_detectorswithStaticConfigResourceDetector)Example use case: Setting
service.name,service.version, anddeployment.environmentfor proper service identification in observability backends like Elastic APM.otel-tui
Release Notes: Yes