Ceki G�lc� wrote:
At 08:25 AM 1/3/2005, Kevin A. Burton wrote:
Ceki G�lc� wrote:
The second more elaborate enhancement comes in the form of filter chains. Define a filter chain which returns a positive value only for logs containing the output from X. When you pass that filter chain to %stacktrace. it should be able to output a stack trace *only* for X, ignoring the other logging events. This will result in a much cleaner log output allowing you to quickly focus on the actual problem.
Here is a configuration file to make my clarify the point.
Wow... that seems like a big CPU hit.
I'd expect the CPU hit to be minimal because the filter chain will only be applied on enabled log statements. For the vast majority of events the filter will not match. In the case of two unequal string, string comparison returns very quickly. I'd go as far as speculating that the CPU hit would be beyond the measurable.
Whats the status of this patch? Was it accepted?
I'm not prepared to do all this extra work because honestly I don't need it for my app. Maybe in the future though..
Kevin
--
Use Rojo (RSS/Atom aggregator). Visit http://rojo.com. Ask me for an invite! Also see irc.freenode.net #rojo if you want to chat.
Rojo is Hiring! - http://www.rojonetworks.com/JobsAtRojo.html
If you're interested in RSS, Weblogs, Social Networking, etc... then you should work for Rojo! If you recommend someone and we hire them you'll get a free iPod!
Kevin A. Burton, Location - San Francisco, CA
AIM/YIM - sfburtonator, Web - http://peerfear.org/
GPG fingerprint: 5FB2 F3E2 760E 70A8 6174 D393 E84D 8D04 99F1 4412
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
