[
https://issues.apache.org/jira/browse/SOLR-16938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17757107#comment-17757107
]
Jan Høydahl commented on SOLR-16938:
------------------------------------
> How might one configure their own tracing customizations without this? E.g.
> custom adapters that redact tags and/or add new tags?
One way could be to read ENV vars or an optional config file from a file
referenced from {{SOLR_TRACING_CONFIG_FILE}} or similar. Or allow an optional
tag in solr.xml for hosting custom config. I'm not 100% clear what an "adapter"
is in this case, is this a feature you plan on adding?
> 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: [email protected]
For additional commands, e-mail: [email protected]
