logging bad stuff separately in resin

[Brian Whitman <br...@variogr.am>]

We have a largish solr index that handles roughly 200K new docs a day  
and also roughly a million queries a day from other programs. It's  
hosted by resin.

A couple of times in the past few weeks something "bad" has happened  
-- a lock error or file handle error, or maybe a required field  
wasn't being sent by the indexer for some reason. We want to be able  
to know about this stuff asap without having to stare at the huge  
resin log all day.

Is there a way to filter the log that goes into resin by "bad/fatal"  
stuff separate from the usual request logging?  I would like to put  
the solr errors somewhere else so it's more maintainable.

Re: logging bad stuff separately in resin

[Chris Hostetter <ho...@fucit.org>]

: Is there a way to filter the log that goes into resin by "bad/fatal" stuff
: separate from the usual request logging?  I would like to put the solr errors
: somewhere else so it's more maintainable.

Resin actually has one of the best logging configuration mechanisms i've 
seen, the docs from caucho should be pretty self explanaitory...

http://www.caucho.com/resin-3.0/config/log.xtp#log

...you can easily modify your resin.conf it up so that SEVERE or WARNING 
logs from sol go some place special, while other messages from solr (or 
other apps) so someplace else.

the one option that *still* seems to be undocumented in the official docs 
is "use-parent-handlers" ... but it does seem to be mentioned in their 
wiki.  in my experience you frequently want it to be "false"...

http://wiki.caucho.com/Log




-Hoss