Skip to content
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

Explicitly define the alternative port 55680 in OpenTelemetry collector configuration file in OpenTelemetry guide #23232

Merged
merged 1 commit into from
Jan 27, 2022

Conversation

soul2zimate
Copy link
Contributor

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 in docker-compose.yml, It turns out that the otel-collector-config.yaml is not receiving from that alternative port 55680. This change just explicitly define that alternative port 55680 in otlp receivers.

…or configuration file in OpenTelemetry guide
@quarkus-bot
Copy link

quarkus-bot bot commented Jan 27, 2022

Thanks for your pull request!

The title of your pull request does not follow our editorial rules. Could you have a look?

  • title should preferably start with an uppercase character (if it makes sense!)

This message is automatically generated by a bot.

@soul2zimate soul2zimate changed the title explicitly define the alternative port 55680 in OpenTelemetry collector configuration file in OpenTelemetry guide Explicitly define the alternative port 55680 in OpenTelemetry collector configuration file in OpenTelemetry guide Jan 27, 2022
@gsmet
Copy link
Member

gsmet commented Jan 27, 2022

Thanks for taking the time to fix that. I wonder if https://github.com/quarkusio/quarkus-quickstarts/tree/main/opentelemetry-quickstart needs some love too? (be careful, use the development branch there)

@soul2zimate
Copy link
Contributor Author

@gsmet gsmet merged commit 35a7cda into quarkusio:main Jan 27, 2022
@quarkus-bot quarkus-bot bot added this to the 2.8 - main milestone Jan 27, 2022
@soul2zimate soul2zimate deleted the opentelemetry branch January 28, 2022 00:47
@gsmet gsmet modified the milestones: 2.8 - main, 2.7.1.Final Jan 31, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants