this is interesting topic. Actually, I want to store similar info/stats
directly into separate ES index and use it for further analysis (one use
case in the future can be query suggestions once they are implemented based
on new Lucene 3.3 API).
Now the question is: what information do you think people usually want to
The obvious candidates would be:
- raw user query text
- may be the QueryDSL that is relevant to the user query (assuming that the
DSL query is not directly built by the user but it is created behind the ES
proxy). So the point here is to track what kind of query is created from
given user input.
- ES response (which includes time, number of hits and error as well as
details for errors, number of involved shards... etc)
may be not very obvious but very useful too (although this has to be
provided by external system):
- user id
- something like "query session" id
- which search result hit did use click
- did user click some suggestions instead of search result hit? (for example
BTW I think Otis G. had an interesting talk about this on #bbuzz this year.
On Wed, Jul 6, 2011 at 7:57 PM, Karussell firstname.lastname@example.org:
Not sure if this is really necessary in Elastics' core, because it is
very simple to feed a stat-index with your own data and build a simple
UI via JS or something around it. I would prefer to see the index feed
as plugin and the UI for that in ES-HEAD
But also if we would have that, requirements of 'stats' are often very
different besides the top terms and query time ...
On 6 Jul., 03:13, Shay Banon shay.ba...@elasticsearch.com wrote:
Yea, you need to do it yourself currently. I do want to build more stats
into search and query times, a bit challenging when it comes to distributed
On Tuesday, July 5, 2011 at 7:37 PM, Karussell wrote:
I'm using the java API where I can use:
If you are not using a layer between ES and your UI I would suggest
that you should do it
not only for security reasons ...