-
Notifications
You must be signed in to change notification settings - Fork 804
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat(otlp-exporter-http): change otlp-http port to canonical 4318 #2557
Conversation
Signed-off-by: secustor <sebastian@poxhofer.at>
Related: #2395 As I understand from the discussions in ☝️, spec intended to stabilize 4317 for the port for OTLP in general? Has it changed? |
I have gone initially simply from the current specification, but it seems there has been some discussion. Speaking from this commit open-telemetry/opentelemetry-specification@90d9aab it seems to be settled on this setup tough. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
IANA is still yet to approve the port reservation.
Although it is in fact following the current spec, I wouldn't rush merging it just yet.
Codecov Report
@@ Coverage Diff @@
## main #2557 +/- ##
=======================================
Coverage 93.22% 93.22%
=======================================
Files 157 157
Lines 5432 5432
Branches 1141 1141
=======================================
Hits 5064 5064
Misses 368 368 |
We definively had some trouble in the past with the back and forth to use one port for both http and grpc so i would like to wait to have a definitive spec to follow before merging this (i guess after IANA will approve the port) |
This PR is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 14 days. |
This PR has many conflicts, but the new collector has probably been out long enough to use the new default port |
According to https://github.com/open-telemetry/opentelemetry-specification/pull/1970/files it looks like the default should also be https? |
Not sure if it is wise to change this, as this could break setups. It is probably the best to wait till a x.0.0 release and change it then. |
doh! I agree we can't really change it now but it is unfortunate. |
Actually because we haven't released the exporter yet as 1.x we can change it. I think we should try to follow spec as closely as possible which would mean using I do question why use |
I have updated all components of those two example to the newest versions and fixed the breaking changes |
Signed-off-by: secustor sebastian@poxhofer.at
Which problem is this PR solving?
Used default port is not the one described in the specification for
opentelemetry-exporter-otlp-http
Reference: https://github.com/open-telemetry/opentelemetry-specification/blob/401bb9c944323d5e3fc773b88ad3319c01abcff0/specification/protocol/exporter.md
Short description of the changes
This PR modifies the default port of the experimental
opentelemetry-exporter-otlp-http
exporter from55681
to the canonical4318
Type of change
How Has This Been Tested?
I have run the test cases using
npm test
Checklist: