[ https://issues.apache.org/jira/browse/SOLR-15367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17742527#comment-17742527 ]
Alex Deparvu commented on SOLR-15367: ------------------------------------- I agree it's wasted effort to do it on top of opentracing, plus adds to the pain of moving to otel. I am reading through SOLR-16536 and can't tell how much work that is, will ask on the ticket. > Convert "rid" functionality into a default Tracer > ------------------------------------------------- > > Key: SOLR-15367 > URL: https://issues.apache.org/jira/browse/SOLR-15367 > Project: Solr > Issue Type: Improvement > Reporter: David Smiley > Assignee: David Smiley > Priority: Major > > Solr's "rid" (request ID) functionality added in SOLR-14566 could be > converted into a distributed-tracing OpenTracing Tracer (Solr > TracerConfigurator) plugin, more or less. Such an implementation, enabled by > default, would merely generate IDs and pass them along in a custom HTTP > header. Solr's existing tracing support would then ensure that this ID is in > MDC in the "t:" log prefix, and thus would fit in nicely. "rid" is kind of a > cheap bolt-on by comparison, duplicative with tracing but far fewer features. > Solr's tracing support is growing, supporting more Solr-to-Solr interaction > than "rid" which is only in a search request. -- 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