# Silence logging altogether for certain actions? **URL:** \ **Category:** Rails\ **Created:** [April 16, 2009, 2:58am UTC](https://www.ruby-forum.com/t/silence-logging-altogether-for-certain-actions/165650 "2009-04-16T02:58:32Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![nwiger](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/n/dbc845/32.png) [@nwiger](https://www.ruby-forum.com/u/nwiger)\ **Post date:** [April 16, 2009, 2:58am UTC](https://www.ruby-forum.com/t/silence-logging-altogether-for-certain-actions/165650/1 "2009-04-16T02:58:32Z")
Hi, I am looking for a way to silence logging altogether for certain actions. Our app talks to other servers and session components, and our logs get filled up with this nonsense, even in Production mode. I want to completely silence all the automatic logging by Rails of the basic request parts: method, params, etc. I’ve seen logger.silence, but that doesn’t appear to get rid of the basic request chatter. Any ideas? Processing ServersController#register to xml (for 127.0.0.1 at 2009-04-15 20:52:17) [POST] Parameters: {“server”=\>{“uname\_node\_name”=\>“domU”, “server\_type”=\>“FLS”, “management\_port”=\>“11054”, “service\_address”=\>“1.2.3.4”, “uname\_version”=\>“#2 SMP Tue Feb 19 10:51:53 EST 2008”, “service\_port”=\>“10054”, “management\_address”=\>“1.2.3.4”, “uname\_sysname”=\>“Linux”, “max\_clients”=\>“2000”, “current\_clients”=\>“2”, “instance\_uuid”=\>“5b7a3804”, “server\_version”=\>“2.1.1/edge (r 2009-04-01 11:13:21) [i686-linux]”, “uname\_domain\_name”=\>“(none)”, “uname\_release”=\>“2.6.18-xenU-ec2-v1.0”, “uname\_machine”=\>“i686”}, “server\_stats”=\>{“cpu\_sys”=\>“0.000000”, “cpu\_nice”=\>“0.000000”, “cpu\_idle”=\>“0.000000”, “cpu\_user”=\>“0.000000”}} Rendering servers/register Completed in 79ms (View: 1, DB: 4) | 200 OK [https:// [ec2.compute-1.amazonaws.com/servers/register.xml](http://ec2.compute-1.amazonaws.com/servers/register.xml)] Processing SessionsController#ping to xml (for 127.0.0.1 at 2009-04-15 20:52:39) [POST] Completed in 16ms (View: 0, DB: 2) | 200 OK [https:// [ec2.compute-1.amazonaws.com/session/ping.xml](http://ec2.compute-1.amazonaws.com/session/ping.xml)] Processing SessionsController#ping to xml (for 127.0.0.1 at 2009-04-15 20:52:41) [POST] Completed in 6ms (View: 0, DB: 2) | 200 OK [https:// [ec2.compute-1.amazonaws.com/session/ping.xml](http://ec2.compute-1.amazonaws.com/session/ping.xml)] Processing ServersController#register to xml (for 127.0.0.1 at 2009-04-15 20:52:47) [POST] Parameters: {“server”=\>{“uname\_node\_name”=\>“domU”, “server\_type”=\>“FLS”, “management\_port”=\>“11054”, “service\_address”=\>“1.2.3.4”, “uname\_version”=\>“#2 SMP Tue Feb 19 10:51:53 EST 2008”, “service\_port”=\>“10054”, “management\_address”=\>“1.2.3.4”, “uname\_sysname”=\>“Linux”, “max\_clients”=\>“2000”, “current\_clients”=\>“2”, “instance\_uuid”=\>“5b7a3804”, “server\_version”=\>“2.1.1/edge (r 2009-04-01 11:13:21) [i686-linux]”, “uname\_domain\_name”=\>“(none)”, “uname\_release”=\>“2.6.18-xenU-ec2-v1.0”, “uname\_machine”=\>“i686”}, “server\_stats”=\>{“cpu\_sys”=\>“0.000000”, “cpu\_nice”=\>“0.000000”, “cpu\_idle”=\>“0.000000”, “cpu\_user”=\>“0.000000”}} Rendering servers/register Completed in 38ms (View: 1, DB: 24) | 200 OK [https:// [ec2.compute-1.amazonaws.com/servers/register.xml](http://ec2.compute-1.amazonaws.com/servers/register.xml)] ---
**Author:** ![nwiger](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/n/dbc845/32.png) [@nwiger](https://www.ruby-forum.com/u/nwiger)\ **Post date:** [April 16, 2009, 6:31pm UTC](https://www.ruby-forum.com/t/silence-logging-altogether-for-certain-actions/165650/2 "2009-04-16T18:31:29Z")
Any ideas? ---
**Author:** ![nwiger](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/n/dbc845/32.png) [@nwiger](https://www.ruby-forum.com/u/nwiger)\ **Post date:** [April 16, 2009, 7:21pm UTC](https://www.ruby-forum.com/t/silence-logging-altogether-for-certain-actions/165650/3 "2009-04-16T19:21:26Z")
One way that might meet your needs is to just up the log level temporarily: … bak\_log\_level = logger.level begin logger.level = :fatal # or some other uppper log level … # stuff you want to perform but restrict logging … … rescue … ensure logger.level = bak\_log\_level end … See > **[Debugging Rails Applications — Ruby on Rails Guides](https://guides.rubyonrails.org/debugging_rails_applications.html)** > > Debugging Rails ApplicationsThis guide introduces techniques for debugging Ruby on Rails applications.After reading this guide, you will know: The purpose of debugging. How to track down problems and issues in your application that your tests aren't... Jeff ---
**Author:** ![nwiger](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/n/dbc845/32.png) [@nwiger](https://www.ruby-forum.com/u/nwiger)\ **Post date:** [April 16, 2009, 7:56pm UTC](https://www.ruby-forum.com/t/silence-logging-altogether-for-certain-actions/165650/4 "2009-04-16T19:56:41Z")
(re-posted) One way that might meet your needs is to just up the log level temporarily: … bak\_log\_level = logger.level begin logger.level = Logger::ERROR # or some other uppper log level … # stuff you want to perform but restrict logging … … rescue … ensure logger.level = bak\_log\_level end … See [Debugging Rails Applications — Ruby on Rails Guides](http://guides.rubyonrails.org/debugging_rails_applications.html#log-l)… Jeff