I stand corrected. The Jetty request logs do indeed contain ALL of the traffic, both from other nodes and from query requests.
For the record, it is valuable to capture the time at the client AND from the server to track latency or compression issues. On 2/11/16, 8:13 AM, "Shawn Heisey" <apa...@elyograg.org> wrote: >On 2/10/2016 10:33 AM, McCallick, Paul wrote: >> We’re trying to fine tune our query and ingestion performance and would like >> to get more metrics out of SOLR around this. We are capturing the standard >> logs as well as the jetty request logs. The standard logs get us QTime, >> which is not a good indication of how long the actual request took to >> process. The Jetty request logs only show requests between nodes. I can’t >> seem to find the client requests in there. >> >> I’d like to start tracking: >> >> * each request to index a document (or batch of documents) and the time >> it took. >> * Each request to execute a query and the time it took. > >The Jetty request log will usually include the IP address of the client >making the request. If IP addresses are included in your log and you >aren't seeing anything from your client address(es), perhaps those >requests are being sent to another node. > >Logging elapsed time is also something that the clients can do. If the >client is using SolrJ, every response object has a "getElapsedTime" >method (and also "getQTime") that would allow the client program to log >the elapsed time without doing its own calculation. Or the client >program could calculate the elapsed time using whatever facilities are >available in the relevant language. > >Thanks, >Shawn >
