i know rails log is very good, detailed. but find useful infos from big log is terrible. any one have good idea. regards -- Posted via http://www.ruby-forum.com/.
On Sat, Mar 11, 2006 at 06:07:55PM +0100, Joe Black wrote:> i know rails log is very good, detailed. > but find useful infos from big log is terrible. > any one have good idea.If you work at it a bit, that would make a great haiku. What kind of information did you have in mind? -- - Adam ** Expert Technical Project and Business Management **** System Performance Analysis and Architecture ****** [ http://www.adamfields.com ] [ http://www.aquick.org/blog ] ............ Blog [ http://www.adamfields.com/resume.html ].. Experience [ http://www.flickr.com/photos/fields ] ... Photos [ http://www.aquicki.com/wiki ].............Wiki
Once you are happy with a noisy section of code do this: logger.silence do # noisy code end Joe Black wrote:> i know rails log is very good, detailed. > but find useful infos from big log is terrible. > any one have good idea. > > regards-- Posted via http://www.ruby-forum.com/.
Adam Fields wrote:> On Sat, Mar 11, 2006 at 06:07:55PM +0100, Joe Black wrote: >> i know rails log is very good, detailed. >> but find useful infos from big log is terrible. >> any one have good idea. > > If you work at it a bit, that would make a great haiku.Data fills the log Signal gets lost in the fog Who can find the way? (sorry...) -- Alex
Log good indeed it is Use grep one must Or something else. On 3/13/06, Alex Young <alex@blackkettle.org> wrote:> > Adam Fields wrote: > > On Sat, Mar 11, 2006 at 06:07:55PM +0100, Joe Black wrote: > >> i know rails log is very good, detailed. > >> but find useful infos from big log is terrible. > >> any one have good idea. > > > > If you work at it a bit, that would make a great haiku. > Data fills the log > Signal gets lost in the fog > Who can find the way? > > (sorry...) > > > -- > Alex > _______________________________________________ > Rails mailing list > Rails@lists.rubyonrails.org > http://lists.rubyonrails.org/mailman/listinfo/rails >-------------- next part -------------- An HTML attachment was scrubbed... URL: http://wrath.rubyonrails.org/pipermail/rails/attachments/20060313/f7b3e673/attachment.html
Joe Black wrote:> i know rails log is very good, detailed. > but find useful infos from big log is terrible. > any one have good idea.Are you running in development mode or in production (which logs a lot less)? Have you seen the comments in config/environment.rb about setting the log level? (If you are still getting too much in your log in production, you could set config.log_level = :warn) For more information, you could start at: http://wiki.rubyonrails.com/rails/pages/logger regards Justin