[ 
https://issues.apache.org/jira/browse/SOLR-5969?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13962997#comment-13962997
 ] 

Erick Erickson commented on SOLR-5969:
--------------------------------------

Just saw SOLR-5971, possibly related? the URL that Eric comments show a url 
with this fragment:
string_months_month&facet=true&q=:,trace=java.lang.IllegalArgumentException

Notice the ,trace= bits.

I have _no_ clue whether it's related in any way, shape or form; just keying 
off the word "trace" here....



> Enable distributed tracing of requests
> --------------------------------------
>
>                 Key: SOLR-5969
>                 URL: https://issues.apache.org/jira/browse/SOLR-5969
>             Project: Solr
>          Issue Type: Improvement
>            Reporter: Gregg Donovan
>         Attachments: SOLR-5969.diff
>
>
> Enable users to add diagnostic information to requests and trace them in the 
> logs across servers.
> We have some metadata -- e.g. a request UUID -- that we log to every log line 
> using Log4J's MDC [1]. The UUID logging allows us to connect any log lines we 
> have for a given request across servers. Sort of like Zipkin [2].
> Currently we're using EmbeddedSolrServer without sharding, so adding the UUID 
> is fairly simple, since everything is in one process and one thread. But, 
> we're testing a sharded HTTP implementation and running into some 
> difficulties getting this data passed around in a way that lets us trace all 
> log lines generated by a request to its UUID.
> The first thing I tried was to add the UUID by adding it to the SolrParams. 
> This achieves the goal of getting those values logged on the shards if a 
> request is successful, but we miss having those values in the MDC if there 
> are other log lines before the final log line. E.g. an Exception in a custom 
> component.
> My current thought is that sending HTTP headers with diagnostic information 
> would be very useful. Those could be placed in the MDC even before handing 
> off to work to SolrDispatchFilter, so that any Solr problem will have the 
> proper logging.
> I.e. every additional header added to a Solr request gets a "Solr-" prefix. 
> On the server, we look for those headers and add them to the SLF4J MDC[3].



--
This message was sent by Atlassian JIRA
(v6.2#6252)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to