[
https://issues.apache.org/jira/browse/SOLR-16354?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17584270#comment-17584270
]
Gus Heck commented on SOLR-16354:
---------------------------------
If we're going to touch tracing, any chance we could also make it an
independent servlet filter wrapping the main filter so it doesn't need to take
up space in and complicate SolrDispatchFilter?
> 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
>
> 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.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org
For additional commands, e-mail: issues-h...@solr.apache.org
