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
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.
The text was updated successfully, but these errors were encountered:
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.
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:
It turned out the
otel-collector
container in the docker-compose was crashing because it didn't likejaeger
as a keyword.Some googling later, I found https://stackoverflow.com/a/77482579/574815 which recommended using
otlp
in place ofjaeger
. Swappingexporters.jaeger
toexporters.otlp
, andservice.pipelines.exporters: [jaeger]
toservice.pipelines.exporters: [otlp]
seems to have solved it for me.The text was updated successfully, but these errors were encountered: