Forum: Ruby on Rails rails log

Announcement (2017-05-07): www.ruby-forum.com is now read-only since I unfortunately do not have the time to support and maintain the forum any more. Please see rubyonrails.org/community and ruby-lang.org/en/community for other Rails- und Ruby-related community platforms.
E13ba8e702211be152c640df2d8e141f?d=identicon&s=25 Joe Black (joe-black)
on 2006-03-11 18:07
i know rails log is very good, detailed.
but find useful infos from big log is terrible.
any one have good idea.

regards
912436ffe7c27e25658a3f5f556a8c96?d=identicon&s=25 Adam Fields (Guest)
on 2006-03-11 18:19
(Received via mailing list)
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
Ef0db53920b243d6758c2f6b1306df0d?d=identicon&s=25 Steve Ross (cwd)
on 2006-03-11 18:35
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
Ad7805c9fcc1f13efc6ed11251a6c4d2?d=identicon&s=25 Alex Young (Guest)
on 2006-03-13 11:52
(Received via mailing list)
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...)
531eb73f8fbf05a197721d02b4e6aadb?d=identicon&s=25 Bogdan Ionescu (Guest)
on 2006-03-13 14:25
(Received via mailing list)
Log good indeed it is
Use grep one must
Or something else.
Eea7ad39737b0dbf3de38874e0a6c7d8?d=identicon&s=25 Justin Forder (Guest)
on 2006-03-14 00:25
(Received via mailing list)
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
This topic is locked and can not be replied to.