[
https://issues.apache.org/jira/browse/SOLR-17432?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Smiley updated SOLR-17432:
--------------------------------
Fix Version/s: main (10.0)
Priority: Blocker (was: Major)
> Enable use of OTEL Agent
> ------------------------
>
> Key: SOLR-17432
> URL: https://issues.apache.org/jira/browse/SOLR-17432
> Project: Solr
> Issue Type: Improvement
> Components: tracing
> Reporter: David Smiley
> Assignee: David Smiley
> Priority: Blocker
> Labels: pull-request-available
> Fix For: main (10.0)
>
> Time Spent: 1h 20m
> Remaining Estimate: 0h
>
> The [OpenTelemetry Java Agent
> |https://opentelemetry.io/docs/zero-code/java/agent/]is really powerful,
> supporting {{WithSpan}} annotations and auto-instrumentation of many
> libraries like the AWS SDK. It also isolates its transitive dependencies in
> another classloader so as not to conflict with Solr's choices. Solr
> currently only supports OTEL via Solr itself calling into OTEL to initialize.
> This ticket proposes _also_ supporting recognizing that the OTEL agent is
> loaded, and if so then using that without any change to solr.xml.
> Without this, someone can write a trivial TracerConfigurator and configure it
> in solr.xml but ideally Solr should detect the situation. If you want to run
> tests with tracing (an overlooked use of tracing!), it's annoying to go touch
> the pertinent 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
