Add endpoint override config options for OTLP HTTP exporter#2089
Merged
albertlockett merged 3 commits intoopen-telemetry:mainfrom Feb 22, 2026
Merged
Conversation
Codecov Report❌ Patch coverage is Additional details and impacted files@@ Coverage Diff @@
## main #2089 +/- ##
=======================================
Coverage 87.04% 87.04%
=======================================
Files 542 542
Lines 174246 174344 +98
=======================================
+ Hits 151666 151762 +96
- Misses 22046 22048 +2
Partials 534 534
🚀 New features to boost your workflow:
|
lalitb
reviewed
Feb 22, 2026
| /// endpoint setting is ignored for traces. | ||
| /// | ||
| /// Example: https://example.com:4318/v1/traces | ||
| pub traces_endpoint: Option<String>, |
Member
There was a problem hiding this comment.
Good to also add validation for these signal-override endpoints in from_config, similar to how we do for 'endpoint`.
Member
Author
lalitb
approved these changes
Feb 22, 2026
albertlockett
force-pushed
the
albert/1145-endpoint-overrides
branch
from
6b0bb89 to
77b800d
Compare
cijothomas
pushed a commit
to cijothomas/otel-arrow
that referenced
this pull request
Feb 23, 2026
…emetry#2089) # Change Summary <!-- Replace with a brief summary of the change in this PR --> small followup from open-telemetry#2070. Adds new config options for each signal type to override the endpoint to which the OTLP HTTP exporter sends data. This is to aid with parity between this implementation and the analogous Go collector component, which also has these options: https://github.com/open-telemetry/opentelemetry-collector/tree/main/exporter/otlphttpexporter#otlp-http-exporter ## What issue does this PR close? <!-- We highly recommend correlation of every PR to an issue --> * Part of open-telemetry#1145 ## How are these changes tested? A new unit test is added. ## Are there any user-facing changes? <!-- If yes, provide further info below --> Users can configure the component with these new options.
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
Change Summary
small followup from #2070.
Adds new config options for each signal type to override the endpoint to which the OTLP HTTP exporter sends data.
This is to aid with parity between this implementation and the analogous Go collector component, which also has these options: https://github.com/open-telemetry/opentelemetry-collector/tree/main/exporter/otlphttpexporter#otlp-http-exporter
What issue does this PR close?
How are these changes tested?
A new unit test is added.
Are there any user-facing changes?
Users can configure the component with these new options.