[jira] [Resolved] (SOLR-16938) Auto configure tracer without a tag in solr.xml

["Alex Deparvu (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/SOLR-16938?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Alex Deparvu resolved SOLR-16938.
---------------------------------
    Fix Version/s: 9.4
       Resolution: Fixed

> Auto configure tracer without a <tracerConfig> tag in solr.xml
> --------------------------------------------------------------
>
>                 Key: SOLR-16938
>                 URL: https://issues.apache.org/jira/browse/SOLR-16938
>             Project: Solr
>          Issue Type: Improvement
>          Components: tracing
>            Reporter: Jan Høydahl
>            Assignee: Alex Deparvu
>            Priority: Major
>             Fix For: 9.4
>
>          Time Spent: 1h
>  Remaining Estimate: 0h
>
> Spinoff from SOLR-16536. It should now be possible to get rid of the explicit {{<tracerConfig>}} config in solr.xml and the pluggable {{TracerConfigurator}} class which is initialized in {{CoreContainer}}.
> Instead, the {{opentelemetry}} plugin can self-register statically to the global OTEL instance.  This will make it sufficient to enable the {{opentelemetry}} module to enable tracing. You can also [enable/disable|https://opentelemetry.io/docs/specs/otel/configuration/sdk-environment-variables/] it with env {{OTEL_SDK_DISABLED}}.
> Alternatively, if we are getting away with global instance (SOLR-16937), then SolrCore could discover the plugin using SPI or similar as opposed to explicit editing of solr.xml.



--
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