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

Grafana example's docker-compose crashes #579

Closed
dylemma opened this issue Apr 4, 2024 · 2 comments · Fixed by #580
Closed

Grafana example's docker-compose crashes #579

dylemma opened this issue Apr 4, 2024 · 2 comments · Fixed by #580

Comments

@dylemma
Copy link

dylemma commented Apr 4, 2024

I was trying out the example project at https://typelevel.org/otel4s/examples/grafana/#config-otel-collector-config-yaml and was getting this in my application:

[error] WARNING: Failed to export spans. Server responded with gRPC status code 2. Error message: Failed to connect to localhost/0:0:0:0:0:0:0:1:4317

It turned out the otel-collector container in the docker-compose was crashing because it didn't like jaeger as a keyword.

otel-collector-1  | * error decoding 'exporters': unknown type: "jaeger" for id: "jaeger" (valid values: [<component.Type Value> <component.Type Value> <component.Type Value> <component.Type Value> <component.Type Value> <component.Type Value> <component.Type Value> <component.Type Value> <component.Type Value> <component.Type Value> <component.Type Value> <component.Type Value> <component.Type Value> <component.Type Value> <component.Type Value> <component.Type Value> <component.Type Value> <component.Type Value> <component.Type Value> <component.Type Value> <component.Type Value> <component.Type Value> <component.Type Value> <component.Type Value> <component.Type Value> <component.Type Value> <component.Type Value> <component.Type Value> <component.Type Value> <component.Type Value> <component.Type Value> <component.Type Value> <component.Type Value> <component.Type Value> <component.Type Value> <component.Type Value> <component.Type Value> <component.Type Value> <component.Type Value> <component.Type Value> <component.Type Value> <component.Type Value> <component.Type Value> <component.Type Value> <component.Type Value> <component.Type Value> <component.Type Value>])
otel-collector-1 exited with code 1

Some googling later, I found https://stackoverflow.com/a/77482579/574815 which recommended using otlp in place of jaeger. Swapping exporters.jaeger to exporters.otlp, and service.pipelines.exporters: [jaeger] to service.pipelines.exporters: [otlp] seems to have solved it for me.

@dylemma
Copy link
Author

dylemma commented Apr 4, 2024

Some time later, I'm not sure the changes I made were necessarily correct. The images run, but I don't get any data in Jaeger when I run the example app.

@iRevive
Copy link
Contributor

iRevive commented Apr 5, 2024

Jaeger exporter has been deprecated in the recent versions of the OTEL collector. We should update the example to use otlp/jaeger https://opentelemetry.io/blog/2023/jaeger-exporter-collector-migration/.

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

Successfully merging a pull request may close this issue.

2 participants