[ https://issues.apache.org/jira/browse/SOLR-16938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17758429#comment-17758429 ]
Jan Høydahl commented on SOLR-16938: ------------------------------------ I was planning on letting the module init by itself into GlobalOpenTelemetry, isolated from corecontainer. But that may clash a bit with your plan in SOLR-15367 I can see. So, having the goals in agreement, I'll let you make some decisions that you feel are ok, without any bike shedding from me :) If that ends up closing this as won't fix for some reason, then be it. > 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: Sub-task > Components: tracing > Reporter: Jan Høydahl > Priority: Major > > 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-unsubscr...@solr.apache.org For additional commands, e-mail: issues-h...@solr.apache.org