-
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
Removing deprecated jaeger and jaegerthrifthttp exporters #26546
Removing deprecated jaeger and jaegerthrifthttp exporters #26546
Conversation
This follows the deprecation plan to remove the component. The original removal date was July 2023, it is now past that. Signed-off-by: Alex Boten <[email protected]>
07a6375
to
33d0a8e
Compare
Signed-off-by: Alex Boten <[email protected]>
Signed-off-by: Alex Boten <[email protected]>
Signed-off-by: Alex Boten <[email protected]>
#26546 removed the jaeger exporter, but the `build-and-test` workflow depended on that exporter since it uses the config in `examples/demo/otel-collector-config.yaml` for its test. This PR updates the demo to use OTLP with jaeger, which also fixes the `rpm` and `deb` test job in `build-and-test`.
I updated to v0.85.0 and Jaeger spanmetrics not working in SPM page, worked fine in v0.84.0 with the same settings. In the official Jaeger's tutorial, they use v0.80.0, but I don't want to roll back to old versions. |
@bangbaew Can you file a separate issue for this? Thanks! |
This follows the deprecation plan to remove the component. The original removal date was July 2023, it is now past that.
Linked issue: open-telemetry/opentelemetry-specification#3551