You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@solr.apache.org by "Jan Høydahl (Jira)" <ji...@apache.org> on 2022/11/09 10:30:00 UTC
[jira] [Updated] (SOLR-16354) Migrate from Jaeger to OTEL tracing
[ https://issues.apache.org/jira/browse/SOLR-16354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jan Høydahl updated SOLR-16354:
-------------------------------
Description:
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.
was:
Jaeger clients are deprecated - [https://www.jaegertracing.io/docs/1.37/client-libraries/#deprecating-jaeger-clients] and it is recommended to migrate to OTEL, see migration guide: [https://opentelemetry.io/docs/migration/opentracing/]
Plan for removing deprecated dependencies (no new functionality):
# Deprecate jaegertracer-configurator
# Replace jaegertracing libs with OTEL libs
# Add the shim that converts existing OpenTracing traces to OpenTelemetry (we can keep the opentracing instrumentation as-is)
# Adapt jaegertracer-configurator so it works as it used to, while using OTEL's Jaeger exporter
Then add a new 'otel' module to Solr, with support for OTEL tracing backend, and possibly other exporters.
As followup tasks, start replacing OpenTracing instrumentation with OTEL equivalents and remove shim.
> Migrate from Jaeger to OTEL tracing
> -----------------------------------
>
> Key: SOLR-16354
> URL: https://issues.apache.org/jira/browse/SOLR-16354
> Project: Solr
> Issue Type: New Feature
> Security Level: Public(Default Security Level. Issues are Public)
> 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: issues-unsubscribe@solr.apache.org
For additional commands, e-mail: issues-help@solr.apache.org