Closed (fixed)
Project:
Apache Solr Search
Version:
6.x-2.x-dev
Component:
Miscellaneous
Priority:
Minor
Category:
Task
Assigned:
Unassigned
Reporter:
Created:
21 Mar 2009 at 00:41 UTC
Updated:
2 Sep 2010 at 16:19 UTC
Jump to comment: Most recent file
Comments
Comment #1
janusman commentedToning this down: it would at *least* be helpful to know long query, MLT, indexing (and other?) operations are taking. Any pointers to existing projects like this one?
Comment #2
Scott Reynolds commentedapphend to the query queryDebug=true and you get a whole lot of useful stuffs
http://wiki.apache.org/solr/CommonQueryParameters#head-f45a9396425956a4d...
Be cool to log some of that away, and only when enabled
edit: i don't believe it works with mlt though :(
Comment #3
robertdouglass commentedA debug mode would be interesting.
Comment #4
janusman commentedFirst proposed patch; this is a contrib module that leverages Apache Solr's hooks to add debugging info. to each query and log query results on query completion.
Instructions:
* Patch applies to 6.x-1.x and 2.x, as does not modify existing files, just adds a new module in contrib/
* Enable the module "Apache Solr Statistics" under admin/build/modules under
* Go to admin/settings/apachesolr/stats and enable logging.
* Do some searches, and go to admin/reports/apachesolr/stats to see the report (see attached sample).
It's still missing quite a lot:
* Want to register clickthrus to report which facets were most valuable to obtain those... this way I'd know a little about what my users are using (and ignoring).
* Want to register clickthrus for the spellchecker suggestions.
* Want to report indexing performance.
Comment #5
janusman commentedIn case someone wants just the contrib/apachesolr_stats folder, here is a ZIP file you can place in your modules/apachesolr/contrib folder (although it'll work fine in sites/all/modules)...
Comment #6
janusman commentedJust a note, the graphs' granularity is "per minute", which will surely break when the log begins to fill up. Will issue a new version soon.
Comment #7
janusman commentedNew patch and .zip file.
Changes: This now uses the shorter data format from Google Charts, so that more points can fit in a single image. It also now aggregates results per hour, not by minute.
Comment #8
robertdouglass commentedcould that be part of the access checking for the report path in hook_menu so you never get to the report if logging isn't enabled?
Comment #9
robertdouglass commentedwith regards to granularity: Something like a set of links to change granularity on the reports page would be great: month | day | hour | minute
And then somehow change this:
$result = db_query_range("SELECT * FROM {apachesolr_stats} ORDER BY timestamp DESC", 0, 1000);
Except... result sets will get really really big. Hmmm.
Comment #10
robertdouglass commentedI know we all trust google... but can we do something to protect this from abusive input?
Peter - do you see any risk here?
Comment #11
robertdouglass commentedAwesome functionality! I think the trend is to make separate projects instead of adding to /contrib. I think you should just make a new project and commit it =)
Comment #12
janusman commentedThanks for your review and help... opened up a new project:
http://drupal.org/project/apachesolr_stats
Closing this out. =)
Comment #13
kenorb commentedSomething similar: #725928: Show the query being generated