[
https://issues.apache.org/jira/browse/SOLR-9641?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15592025#comment-15592025
]
David Smiley commented on SOLR-9641:
------------------------------------
Docs:
* javadocs: probably on the Tracer field you added to core container.
TracerUtils.java should refer to that so people know where it's placed in Solr.
* user docs: we'll probably want to add this to the ref guide... at least
something very brief that can demonstrate the simplest useful way to see it in
action, and then we refer users to other possibilities (i.e. ZipKin). There
ought to be a reference to this feature in the vicinity of where
debugQuery/debug=timing is so people know of this more sophisticated option.
> Emit distributed tracing information from Solr
> ----------------------------------------------
>
> Key: SOLR-9641
> URL: https://issues.apache.org/jira/browse/SOLR-9641
> Project: Solr
> Issue Type: Improvement
> Security Level: Public(Default Security Level. Issues are Public)
> Reporter: Mike Drob
> Fix For: master (7.0)
>
> Attachments: SOLR-9641.patch
>
>
> While Solr already offers a few tools for exposing timing, this information
> can be difficult to aggregate and analyze. By integrating distributed tracing
> into Solr operations, we can gain new performance and behaviour insights.
> One such solution can be accomplished via Apache HTrace (incubating).
> (More rationale to follow.)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
