Re: dealing with logs - feature advice based on a use case

[Otis Gospodnetic <ot...@yahoo.com>]

Marc,

I don't have a Multicore setup that's itching for better logging, but I think what you are suggesting is good.  If I had a multicore setup I might want either separate logs or the option to log the core name.  Perhaps an Enhancement type JIRA entry is in order?

Otis --
Sematext -- http://sematext.com/ -- Lucene - Solr - Nutch 




________________________________
From: Marc Sturlese <ma...@gmail.com>
To: solr-user@lucene.apache.org
Sent: Wednesday, January 14, 2009 11:54:09 PM
Subject: dealing with logs - feature advice based on a use case


Hey there,
Just want to explain a feature I think would be really useful for the
future.
In my use case I need a log per core. I spoke about this feature before. My
idea was to separate the logs with log4j but saw it was not that easy. In
the other thread we spoke about passing the core name to the loggers. Do
that would be so much hacking so I decided not to do that (otherwise would
be almost impossible to upgrade to new releases). I think would be great to
have it in Solr.

To solve it, what I have done is use log4j and log all messages in the
syslog. Once in there I have bash scripts that redirect the messages
depending on the core name they have. Apparently this would solve my problem
but there are lots of messages that haven't the core name so I can't
redirect them to the needed log file.
So, another possible solution would be to have the core name in all log
messages.

Don't you think would be useful in many use cases?
Thanks in advance
-- 
View this message in context: http://www.nabble.com/dealing-with-logs---feature-advice-based-on-a-use-case-tp21458747p21458747.html
Sent from the Solr - User mailing list archive at Nabble.com.