-
Notifications
You must be signed in to change notification settings - Fork 896
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
Change default OTLP port number #1221
Change default OTLP port number #1221
Conversation
cb01c3f
to
e92112e
Compare
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.
Please also update the default mentioned in specification/protocol/exporter.md#configuration-options
and the examples below.
Should we add a compliance matrix entry for using the correct default port?
This implements specification change open-telemetry/opentelemetry-specification#1221 To make transition to new port numbers less painful OTLP receiver will also accept data on the legacy port numbers when it is configured to use the default endpoint. Users who use the default Collector config can continue sending data to the legacy ports and have a graceful period to update their senders to start sending to the new ports. Note that OTLP/HTTP continues using a separate port number from OTLP/gRPC. There is separate work in progress to use one port for both.
This implements specification change open-telemetry/opentelemetry-specification#1221 To make transition to new port numbers less painful OTLP receiver will also accept data on the legacy port numbers when it is configured to use the default endpoint. Users who use the default Collector config can continue sending data to the legacy ports and have a graceful period to update their senders to start sending to the new ports. Note that OTLP/HTTP continues using a separate port number from OTLP/gRPC. There is separate work in progress to use one port for both.
This implements specification change open-telemetry/opentelemetry-specification#1221 To make transition to new port numbers less painful OTLP receiver will also accept data on the legacy port numbers when it is configured to use the default endpoint. Users who use the default Collector config can continue sending data to the legacy ports and have a graceful period to update their senders to start sending to the new ports. Note that OTLP/HTTP continues using a separate port number from OTLP/gRPC. There is separate work in progress to use one port for both.
This implements specification change open-telemetry/opentelemetry-specification#1221 To make transition to new port numbers less painful OTLP receiver will also accept data on the legacy port numbers when it is configured to use the default endpoint. Users who use the default Collector config can continue sending data to the legacy ports and have a graceful period to update their senders to start sending to the new ports. Note that OTLP/HTTP continues using a separate port number from OTLP/gRPC. There is separate work in progress to use one port for both.
This implements specification change open-telemetry/opentelemetry-specification#1221 To make transition to new port numbers less painful OTLP receiver will also accept data on the legacy port numbers when it is configured to use the default endpoint. Users who use the default Collector config can continue sending data to the legacy ports and have a graceful period to update their senders to start sending to the new ports. Note that OTLP/HTTP continues using a separate port number from OTLP/gRPC. There is separate work in progress to use one port for both.
Corresponding change in the Collector, allowing to receive on new and legacy ports simultaneously to ease the transition open-telemetry/opentelemetry-collector#2104 |
Done.
I added this to the CHANGELOG, hopefully it is sufficient. |
@tigrannajaryan is the number confirmed? |
@mtwo submitted the request with IANA. It will take a while to get the confirmation. I think we should move forward with the assumption that it will be accepted. On the minor chance that it will be rejected and a different port number suggested we can update the spec again, we still have time. |
ada6e24
to
ca65854
Compare
+1 |
@open-telemetry/specs-approvers Anybody objects to going forward with this proposal, given that the request with IANA has been filled but it may take a while to get a confirmation? If not, I suggest merging early tomorrow or on Monday. |
This implements specification change open-telemetry/opentelemetry-specification#1221 To make transition to new port numbers less painful OTLP receiver will also accept data on the legacy port numbers when it is configured to use the default endpoint. Users who use the default Collector config can continue sending data to the legacy ports and have a graceful period to update their senders to start sending to the new ports. Note that OTLP/HTTP continues using a separate port number from OTLP/gRPC. There is separate work in progress to use one port for both.
sgtm I actually care less about having an official IANA port than about not using ephemeral port, because the latter has a higher chance of causing instability at deployment. |
@bogdandrutu Any opinion? ;) |
This implements specification change open-telemetry/opentelemetry-specification#1221 To make transition to new port numbers less painful OTLP receiver will also accept data on the legacy port numbers when it is configured to use the default endpoint. Users who use the default Collector config can continue sending data to the legacy ports and have a graceful period to update their senders to start sending to the new ports. Note that OTLP/HTTP continues using a separate port number from OTLP/gRPC. There is separate work in progress to use one port for both.
SGTM, let's merge this. |
specification/protocol/otlp.md
Outdated
@@ -445,7 +445,7 @@ connections SHOULD be configurable. | |||
|
|||
#### Default Port | |||
|
|||
The default network port for OTLP/HTTP is 55681. There is currently an [open | |||
The default network port for OTLP/HTTP is 4318. There is currently an [open |
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.
Did we not say that we try to not have 2 ports?
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.
Ping @tigrannajaryan
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.
Fixed.
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.
The spec now lists the same port for both OTLP/gRPC and OTLP/HTTP.
Contributes to open-telemetry#1148 Note that a separate port is used for OTLP/HTTP for now. There is currently work in progress to confirm that we can use the same port. Once we have the confirmation I will update the spec again to use one port.
ca65854
to
ba86535
Compare
Since now we have the two-ports update, it looks we are ready to merge today, right? @tigrannajaryan @bogdandrutu |
ba86535
to
ac800f1
Compare
4 approves + author (TC member) - merging |
This implements specification change open-telemetry/opentelemetry-specification#1221 To make transition to new port numbers less painful OTLP receiver will also accept data on the legacy port numbers when it is configured to use the default endpoint. Users who use the default Collector config can continue sending data to the legacy ports and have a graceful period to update their senders to start sending to the new ports. Note that OTLP/HTTP continues using a separate port number from OTLP/gRPC. There is separate work in progress to use one port for both.
This implements specification change open-telemetry/opentelemetry-specification#1221 To make transition to new port numbers less painful OTLP receiver will also accept data on the legacy port numbers when it is configured to use the default endpoint. Users who use the default Collector config can continue sending data to the legacy ports and have a graceful period to update their senders to start sending to the new ports. Note that OTLP/HTTP continues using a separate port number from OTLP/gRPC. There is separate work in progress to use one port for both.
This implements specification change open-telemetry/opentelemetry-specification#1221 To make transition to new port numbers less painful OTLP receiver will also accept data on the legacy port numbers when it is configured to use the default endpoint. Users who use the default Collector config can continue sending data to the legacy ports and have a graceful period to update their senders to start sending to the new ports. Note that OTLP/HTTP continues using a separate port number from OTLP/gRPC. There is separate work in progress to use one port for both.
From specification - open-telemetry/opentelemetry-specification#1221
4317 is now the default port for OLTP gRPC, as open-telemetry/opentelemetry-specification#1221
* Change default OTLP port number Contributes to open-telemetry#1148 Note that a separate port is used for OTLP/HTTP for now. There is currently work in progress to confirm that we can use the same port. Once we have the confirmation I will update the spec again to use one port. * Address PR comments
Contributes to #1148
Note that a separate port is used for OTLP/HTTP for now. There is currently work
in progress to confirm that we can use the same port. Once we have the confirmation
I will update the spec again to use one port.