You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@solr.apache.org by "David Smiley (Jira)" <ji...@apache.org> on 2023/11/03 18:34:00 UTC

[jira] [Updated] (SOLR-16943) Tracing: cover more flows by moving instrumentation down to our HttpClient implies

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

David Smiley updated SOLR-16943:
--------------------------------
    Summary: Tracing: cover more flows by moving instrumentation down to our HttpClient implies  (was: Add client tracing spans to HTTP interaction; at least for Jetty HttpClient)

> Tracing: cover more flows by moving instrumentation down to our HttpClient implies
> ----------------------------------------------------------------------------------
>
>                 Key: SOLR-16943
>                 URL: https://issues.apache.org/jira/browse/SOLR-16943
>             Project: Solr
>          Issue Type: Improvement
>          Components: tracing
>            Reporter: David Smiley
>            Priority: Major
>          Time Spent: 6h 10m
>  Remaining Estimate: 0h
>
> Instead of injecting tracing at HttpShardHandler & SolrCmdDistributor, go deeper at InstrumentedHttpListenerFactory, thereby covering more use-cases.  A random example is org.apache.solr.update.processor.DistributedUpdateProcessor#fetchFullUpdateFromLeader which currently isn't traced.



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