[
https://issues.apache.org/jira/browse/SOLR-8274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17137783#comment-17137783
]
David Smiley commented on SOLR-8274:
------------------------------------
I'm an OpenTracing noob too but what drives me is the desire for the principle
of having one way to transmit a tracking ID. Some of the work [~caomanhdat]
did here to make OpenTracing work ought to be useful for passing along any
tracing ID. At least in principle and I hope in practice. Lets not do
redundant work (redundant code paths for similar things). I appreciate that
OpenTracing specifically might really only be about a tracing server and
sampling; I'm not sure.
> Add per-request MDC logging based on user-provided value.
> ---------------------------------------------------------
>
> Key: SOLR-8274
> URL: https://issues.apache.org/jira/browse/SOLR-8274
> Project: Solr
> Issue Type: Improvement
> Components: logging
> Reporter: Jason Gerlowski
> Priority: Minor
> Attachments: SOLR-8274.patch
>
>
> *Problem 1* Currently, there's no way (AFAIK) to find all log messages
> associated with a particular request.
> *Problem 2* There's also no easy way for multi-tenant Solr setups to find all
> log messages associated with a particular customer/tenant.
> Both of these problems would be more manageable if Solr could be configured
> to record an MDC tag based on a header, or some other user provided value.
> This would allow admins to group together logs about a single request. If
> the same header value is repeated multiple times this functionality could
> also be used to group together arbitrary requests, such as those that come
> from a particular user, etc.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org
