-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
v0.85.0 fails to unmarshall jaeger exporter #26685
Comments
The Jaeger exporter was deprecated in the spec on open-telemetry/opentelemetry-specification/pull/2858 and in the Collector on #18503, since Jaeger now supports OTLP natively so you can use the OTLP exporter. v0.85.0 removes the exporter see open-telemetry/opentelemetry-collector-releases/pull/396 but we did not list this in the changelog because the associated PR in contrib (#26546) did not make it in v0.85.0. We should add a changelog entry about this. Regardless of the changelog note, please switch to using the OTLP exporter instead! |
The changelog for the v0.85.0 release https://github.com/open-telemetry/opentelemetry-collector-releases/releases/tag/v0.85.0 includes the change to remove the exporter. |
Sorry for the confusion, since it is actually documented on the '-releases' changelog I am going to close this as wontfix |
To help address the confusion i've added a PR to the docs repo open-telemetry/opentelemetry.io#3273 |
Describe the bug
v0.85.0 fails to decode jaeger exporter. Collector logs:
Steps to reproduce
Docker compose:
otel-collector.yml:
run:
docker compose up
What did you expect to see?
Collector should work as it was working on 0.84.0
What did you see instead?
Collector fails to init.
What version did you use?
v0.85.0
What config did you use?
Config:
Environment
Docker
OS:
ProductName: macOS
ProductVersion: 13.2
The text was updated successfully, but these errors were encountered: