Hello - This patch may be more straightforward
https://issues.apache.org/jira/browse/SOLR-4018
-----Original message-----
> From:Ahmed Adel <ahmed.a...@badrit.com>
> Sent: Wednesday 4th March 2015 19:39
> To: solr-user@lucene.apache.org
> Subject: Re: Log numfound, qtime, ...
>
> Hi, I believe a better approach than Solarium is to create a custom search
> component that extends SearchComponent class and override process() method
> to store query, QTime, and numFound to a database for further analysis.
> This approach would cut steps 2 through 6 into one step. Analysis can be
> done using Banana (https://github.com/LucidWorks/banana) analytics and
> search dashboard.
>
> On Fri, Feb 27, 2015 at 1:36 PM, Mikhail Khludnev <
> mkhlud...@griddynamics.com> wrote:
>
> > Did you check Kibana/Banana ?
> >
> > On Fri, Feb 27, 2015 at 2:07 PM, bengates <benga...@aliceadsl.fr> wrote:
> >
> > > Hello everyone,
> > >
> > > Here's my need : I'd like to log Solr Responses so as to achieve some
> > > business statistics.
> > > I'd like to report, as a daily/weekly/yearly/whateverly basis, the
> > > following
> > > KPIs :
> > > - Most popular requests (hits)
> > > - Average numfound for each request
> > > - Average response time for each request
> > > - Requests that have returned an error
> > > - Request that have a numfound of 0.
> > >
> > > The idea is to give the searchandizer the keys to analyze and enhance in
> > > real-time the relevancy of his data. I think it's not the job of a
> > > developer
> > > to detect that the keyword TV never has results because "Television" is
> > the
> > > referring word in the whole catalog, for instance. The searchandizer
> > should
> > > analyze this at anytime and provide the correct synonyms to improve
> > > relevance.
> > >
> > > I'm using Solr with PHP and the Solarium library.
> > > Actually the only way I found to manage this, is the following way :
> > >
> > > 1. The user sends the request
> > > 2. Nginx intercepts the request, and forwards it to a PHP app
> > > 3. The PHP app loads the Solarium library and forwards the request to
> > > Solr/Jetty
> > > 4. Solr replies a JSON and Solarium turns it into a PHP Solarium Response
> > > Object
> > > 5. The PHP app sends the user the raw JSON through NGINX (as if it were
> > > Jetty)
> > > 6. The PHP app stores the query, the QTime and the numfound in a database
> > >
> > > I think I'll soon get into performance issues, as you guess.
> > > Do you know a better approach ?
> > >
> > > Thanks,
> > > Ben
> > >
> > >
> > >
> > > --
> > > View this message in context:
> > > http://lucene.472066.n3.nabble.com/Log-numfound-qtime-tp4189561.html
> > > Sent from the Solr - User mailing list archive at Nabble.com.
> > >
> >
> >
> >
> > --
> > Sincerely yours
> > Mikhail Khludnev
> > Principal Engineer,
> > Grid Dynamics
> >
> > <http://www.griddynamics.com>
> > <mkhlud...@griddynamics.com>
> >
>
>
>
> --
> A. Adel
>
