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

Jaeger: no http client #421

Closed
VendettaReborn opened this issue May 20, 2024 · 1 comment
Closed

Jaeger: no http client #421

VendettaReborn opened this issue May 20, 2024 · 1 comment

Comments

@VendettaReborn
Copy link
Contributor

VendettaReborn commented May 20, 2024

when enabling jaeger via "JAGER_ENDPOINT", i encountered the error:
failed to setup logging: Exporter otlp encountered the following error(s): no http client, you must select one from features or provide your own implementation

it seems that otlp_exporter missed the calling of with_http_client, there are two ways of fixing this:

  1. use grpc client instead of http client (tonic has already been a dependency in other places, so won't lead to extra imports)
  2. add deps of opentelemetry_http, create a client and pass it to with_http_client

the former one is simplier, but the jaeger's startup command has to be changed into:
docker run -d -p16686:16686 -p4317:4317 -p4318:4318 -e COLLECTOR_OTLP_ENABLED=true jaegertracing/all-in-one:latest to use the grpc port 4317 (so the docs should also be updated)

@ibigbug
Copy link
Member

ibigbug commented May 22, 2024

Yeah it's a known issue. open-telemetry/opentelemetry-rust#1659 (comment)

Maybe time to move to the grpc transport.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants