[
https://issues.apache.org/jira/browse/SOLR-16536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17654669#comment-17654669
]
Jan Høydahl commented on SOLR-16536:
------------------------------------
According to
[https://opentelemetry.io/docs/migration/opentracing/#step-2-progressively-replace-instrumentation]
{quote}What about existing instrumentation? There is no hard requirement to
migrate existing application code to OpenTelemetry. However, we do recommend
migrating from any OpenTracing instrumentation libraries – libraries used to
instrument web frameworks, HTTP clients, database clients, etc. – to their
OpenTelemetry equivalents. This will improve support, as many OpenTracing
libraries will be retired and may no longer be updated.
{quote}
I'm not familiar with our OpenTracing instrumentation but I find 81 matches
when searching codebase for 'io.opentracing'. Will need to use something else
than 'GlobalTracer'. I believe OTEL provides an SPI mechanism for plugging in
tracers.
Also need to figure out how this will work with e.g. DataDog agent, if they
have one for OTEL that will provide an SPI tracer that will be auto loaded etc,
and change documentation accordingly.
> Replace OpenTracing instrumentation with OpenTelemetry
> ------------------------------------------------------
>
> Key: SOLR-16536
> URL: https://issues.apache.org/jira/browse/SOLR-16536
> Project: Solr
> Issue Type: Sub-task
> Security Level: Public(Default Security Level. Issues are Public)
> Reporter: Jan Høydahl
> Priority: Major
>
> After this, we do not have any traces (pun intended) of either OpenTracing or
> Jaegertracer libraries in Solr. We'll be using OTEL java sdk both for
> instrumentation and trace exporting.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
