Hello everyone,
I'll check this ASAP.
Thanks for all your answers !
Ben
--
View this message in context:
http://lucene.472066.n3.nabble.com/Log-numfound-qtime-tp4189561p4191129.html
Sent from the Solr - User mailing list archive at Nabble.com.
: 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 :
...
: I think I'll soon get into performance issues, as you guess.
: Do you know a better approach ?
All of this
Hello - This patch may be more straightforward
https://issues.apache.org/jira/browse/SOLR-4018
-Original message-
> From:Ahmed Adel
> Sent: Wednesday 4th March 2015 19:39
> To: solr-user@lucene.apache.org
> Subject: Re: Log numfound, qtime, ...
>
> Hi, I believe
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
Did you check Kibana/Banana ?
On Fri, Feb 27, 2015 at 2:07 PM, bengates 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 pop
