You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
opentelemetry-exporter-collector-proto should probably use port 55681 to match opentelemetry-collector.
What did you see instead?
I observed that the SDK will error out if opentelemetry-exporter-collector-proto is configured to send HTTP to the gRPC port running 4317 because they are not compatible.
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered:
Please answer these questions before submitting a bug report.
What version of OpenTelemetry are you using?
0.23.0
What version of Node are you using?
14
Please provide the code you used to setup the OpenTelemetry SDK
What did you do?
The opentelemetry-collector has default OTLP receivers for gRPC run on port
4317
and HTTP run on55681
https://github.com/open-telemetry/opentelemetry-collector/blob/f3784a92def81ae9b5c770c97ac2d5bed4f9b804/receiver/otlpreceiver/factory.go#L33-L34
The port for gRPC is outlined in the specs:
https://github.com/open-telemetry/opentelemetry-specification/blob/2a712f7626cb62b21ae210ef3175612e7744f285/specification/protocol/otlp.md#otlpgrpc-default-port
The JavaScript
opentelemetry-exporter-collector-grpc
package correctly exports gRPC to4317
:opentelemetry-js/packages/opentelemetry-exporter-collector-grpc/src/CollectorTraceExporter.ts
Line 28 in 3a327dd
However, the JavaScript
opentelemetry-exporter-collector-proto
clashes because it tries to export HTTP to the4317
port reserved for gRPC:opentelemetry-js/packages/opentelemetry-exporter-collector-proto/src/CollectorMetricExporter.ts
Line 27 in 3a327dd
What did you expect to see?
opentelemetry-exporter-collector-proto
should probably use port55681
to match opentelemetry-collector.What did you see instead?
I observed that the SDK will error out if
opentelemetry-exporter-collector-proto
is configured to send HTTP to the gRPC port running4317
because they are not compatible.Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: