On Mar 30, 2010, at 2:43 PM, Peter S wrote:
I have an existing QParserPlugin subclass that does some tagging
functionality (kind of a group alias thing). This is currently
registered with the default queryHandler.
I want to add another, quite separate plugin that writes an audit of
every query request that comes in.
Sounds like what you want is a SearchComponent, not a QParserPlugin.
You'll have to plug it into each request handler in the config
though. or...
Being able to track what has happened on a Solr instance in a non-
repudiated fashion would be [hopefully] useful for others as well
(e.g. if you're storing/accessing secure documents and need to know
every time someone accesses something). I know there is some logging
that tracks requests etc., but log files are difficult to secure in
a forensically-legal way. Maybe whatever generates the log entries
can be plugged into so that secure, 'tamper-proof' audit trails can
be generated?
The logging is able to be hooked, so you could write your own log
handler to write the events elsewhere. This is left as an exercise
for the reader, since it will depend on which logging framework
employed.
Erik
