[
https://issues.apache.org/jira/browse/SOLR-16354?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17756004#comment-17756004
]
Jan Høydahl commented on SOLR-16354:
------------------------------------
In 9.x we still have jaegertracer module, which has hard dependencies to
OpenTracing libs, so we cannot remove OpenTracing in 9.x.
Also, we should not change user facing configuration format in 9.x. If someone
are using our "opentelemetry" module for tracing in 9.3, they should be able to
run it with same config, same environment variables, emitting the same tag
names and the same spans as in 9.x throughout 9.x.
Adding new spans to fill gaps is not taking anything away, but adding a more
rich trace output, so I think that would be acceptable.
Back compat means we should answer "yes" to the question "Can a user upgrade
from 9.x to 9.y without any config changes, and experience no disruption"?
> Migrate from Jaeger/OpenTracing to OTEL
> ---------------------------------------
>
> Key: SOLR-16354
> URL: https://issues.apache.org/jira/browse/SOLR-16354
> Project: Solr
> Issue Type: New Feature
> Affects Versions: 9.0
> Reporter: Jan Høydahl
> Priority: Major
> Labels: opentelemetry, otel, tracing
> Time Spent: 1h 20m
> Remaining Estimate: 0h
>
> Umbrella issue for introducing OTEL (OpenTelemetry) in Solr.
> Solr-core has OpenTracing instrumentation. And in jaegertracer-configurator
> module, we use the Jaeger client to export traces on Jaeger/Thrift format.
> Jaeger clients are deprecated -
> [https://www.jaegertracing.io/docs/1.37/client-libraries/#deprecating-jaeger-clients]
> and the world is anyway moving to OTEL/OTLP protocol for tracing.
> Here is a proposed path forward:
> h3. Phase 1 - getting rid of the deprecated jaeger client
> We'll keeping OpenTracing instrumentation in solr-core. Using the
> opentelemetry-opentracing shim we can use OTEL java-client instead.
> # Introduce a new 'otel' module, exposing an OTLP trace exporter (grpc or
> http)
> # Add otel-jaeger exporter support to the 'otel' module for those who still
> need it
> # Deprecate the 'jaegertracer-configurator' for removal in 10.0 (since
> jaeger-client will be very dead by then)
> # Remove jaegertracer-configurator in main
> # Optionally we can quite easily add Zipkin or other support using the OTEL
> java client as well
> h3. Phase 2 - replace OpenTracing instrumentation with OTEL instrumentation
> it is recommended to migrate instrumentation from OTO to OTEL, see migration
> guide: [https://opentelemetry.io/docs/migration/opentracing/]
> Once that is done, the 'otel' module will expose the OTEL "Tracer" instead of
> the OT "Tracer" through shim.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
