# Rails log

**URL:** <https://www.ruby-forum.com/t/rails-log/79901>\
**Category:** Rails\
**Created:** [March 11, 2006, 6:07pm UTC](https://www.ruby-forum.com/t/rails-log/79901 "2006-03-11T18:07:55Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![joe-black](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/j/87869e/32.png) [@joe-black](https://www.ruby-forum.com/u/joe-black)\
**Post date:** [March 11, 2006, 6:07pm UTC](https://www.ruby-forum.com/t/rails-log/79901/1 "2006-03-11T18:07:55Z")

</div>

i know rails log is very good, detailed.  
but find useful infos from big log is terrible.  
any one have good idea.

regards

---

<div class="post-metadata">

**Author:** ![joe-black](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/j/87869e/32.png) [@joe-black](https://www.ruby-forum.com/u/joe-black)\
**Post date:** [March 11, 2006, 6:19pm UTC](https://www.ruby-forum.com/t/rails-log/79901/2 "2006-03-11T18:19:56Z")

</div>

On Sat, Mar 11, 2006 at 06:07:55PM +0100, Joe B. 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.adamfields.com) ]

[[Adam Fields (weblog) - - entertaining hundreds of millions of eyeball atoms every day](http://www.aquick.org/blog) ] … Blog  
[[Adam Fields Resume](http://www.adamfields.com/resume.html) ]… Experience  
[[Adam Fields | Flickr](http://www.flickr.com/photos/fields) ] … Photos  
[[http://www.aquicki.com/wiki](http://www.aquicki.com/wiki) ]…Wiki

---

<div class="post-metadata">

**Author:** ![joe-black](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/j/87869e/32.png) [@joe-black](https://www.ruby-forum.com/u/joe-black)\
**Post date:** [March 11, 2006, 6:35pm UTC](https://www.ruby-forum.com/t/rails-log/79901/3 "2006-03-11T18:35:32Z")

</div>

Once you are happy with a noisy section of code do this:

logger.silence do

# noisy code

end

Joe B. wrote:

> i know rails log is very good, detailed.  
> but find useful infos from big log is terrible.  
> any one have good idea.
> 
> regards

---

<div class="post-metadata">

**Author:** ![joe-black](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/j/87869e/32.png) [@joe-black](https://www.ruby-forum.com/u/joe-black)\
**Post date:** [March 13, 2006, 11:52am UTC](https://www.ruby-forum.com/t/rails-log/79901/4 "2006-03-13T11:52:09Z")

</div>

Adam F. wrote:

> On Sat, Mar 11, 2006 at 06:07:55PM +0100, Joe B. 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…)

---

<div class="post-metadata">

**Author:** ![joe-black](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/j/87869e/32.png) [@joe-black](https://www.ruby-forum.com/u/joe-black)\
**Post date:** [March 14, 2006, 12:25am UTC](https://www.ruby-forum.com/t/rails-log/79901/5 "2006-03-14T00:25:06Z")

</div>

Joe B. 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:

[Peak Obsession](http://wiki.rubyonrails.com/rails/pages/logger)

regards

Justin

---

<div class="post-metadata">

**Author:** ![joe-black](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/j/87869e/32.png) [@joe-black](https://www.ruby-forum.com/u/joe-black)\
**Post date:** [March 13, 2006, 2:25pm UTC](https://www.ruby-forum.com/t/rails-log/79901/6 "2006-03-13T14:25:07Z")

</div>

Log good indeed it is  
Use grep one must  
Or something else.