We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
otlptracehttp client defaults to port 4317, but collector spec says http uses 4318. (4317 is for grpc).
opentelemetry-go/exporters/otlp/otlptrace/otlptracehttp/options.go
Line 58 in bd817df
endpoint (default = 0.0.0.0:4317 for grpc protocol, 0.0.0.0:4318 http protocol):
go.opentelemetry.io/otel/exporters/otlp/otlptrace v1.4.0 go.opentelemetry.io/otel/exporters/otlp/otlptrace/otlptracehttp v1.4.0 go.opentelemetry.io/otel/sdk v1.4.0 go.opentelemetry.io/otel/trace v1.4.0
I would expect the http client to default to port 4318, such that it is aligned with the port expected by the collector.
The text was updated successfully, but these errors were encountered:
The OpenTelemetry specification also states the port 4318 should be used as the default for HTTP.
4318
This is currently unified in the internal/otlpconfig package.
internal/otlpconfig
opentelemetry-go/exporters/otlp/otlptrace/internal/otlpconfig/optiontypes.go
Line 20 in 1bda062
It will need to be refactored to support different default values for the different clients.
Sorry, something went wrong.
MrAlias
Successfully merging a pull request may close this issue.
Description
otlptracehttp client defaults to port 4317, but collector spec says http uses 4318. (4317 is for grpc).
opentelemetry-go/exporters/otlp/otlptrace/otlptracehttp/options.go
Line 58 in bd817df
endpoint (default = 0.0.0.0:4317 for grpc protocol, 0.0.0.0:4318 http protocol):
,Environment
Steps To Reproduce
Expected behavior
I would expect the http client to default to port 4318, such that it is aligned with the port expected by the collector.
The text was updated successfully, but these errors were encountered: