Explicitly define the alternative port 55680 in OpenTelemetry collector configuration file in OpenTelemetry guide #23232
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.
When I run the OpenTelemetry guide in https://quarkus.io/version/main/guides/opentelemetry, more specifically, configuring the OTLP gRPC endpoint via JVM arguments with the alternative port
55680
via command./mvnw compile quarkus:dev -Djvm.args="-Dquarkus.opentelemetry.tracer.exporter.otlp.endpoint=http://localhost:55680"
I can see this error:
2022-01-27 17:35:28,399 SEVERE [io.ope.exp.otl.int.grp.DefaultGrpcExporter] (grpc-default-executor-1) Failed to export spans. Server is UNAVAILABLE. Make sure your collector is running and reachable from this network. Full error message:UNAVAILABLE: io exception
Although
OTLP gRPC receiver alternative port 55680
is defined indocker-compose.yml
, It turns out that theotel-collector-config.yaml
is not receiving from that alternative port55680
. This change just explicitly define that alternative port55680
in otlp receivers.