[
https://issues.apache.org/jira/browse/SOLR-16354?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17742528#comment-17742528
]
Alex Deparvu commented on SOLR-16354:
-------------------------------------
[~janhoy] I wanted to build some poc for SOLR-15367, then (with a small nudge
from [~dsmiley]) realized it doesn't make much sense to build anything on top
of opentracing when Solr is in the middle of a transition to otel. do you have
a feel of what work remains to be done here? I don't have a lot of experience
with either tracing solutions, but would be happy to lend a hand if you could
provide some guidance.
> 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
>
> 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]
