Disable Rack::CommonLogger without monkey patching

Question

So, I want to have completely custom logging for my sinatra application, but I can't seem to disable the Rack::CommonLogger.

As per the sinatra docs all I should need to do is add the following line (tried setting it to false as well):

set :logging, nil

to my configuration. This does not work however, and I still receive the Apache-like log messages in my terminal. So the only solution I've found so far is to monkey patch the damn thing.

module Rack
  class CommonLogger
    def call(env)
      # do nothing
      @app.call(env)
    end
  end
end

Anyone got any ideas if it's possible to disable this without restorting to such matters?

from doc `"To avoid any logging middleware to be set up, set the logging setting to nil."` — Roman Kiselenko, Mar 06 '14 at 09:29
I tried that, as well as setting it to ´false´. Didn't work. — nicohvi, Mar 06 '14 at 09:32
Just to be sure, you set these in a configure block which get executed? — Sir l33tname, Mar 06 '14 at 11:37
Yeah, all other commands in the `configure do` block get executed. — nicohvi, Mar 06 '14 at 11:58
What server are you using (thin, webrick etc.) and how are you starting the app (`ruby my_file.rb`, `rackup` etc.)? — matt, Mar 06 '14 at 14:01
I'm using `puma` and I start the server with the command `puma -p 3001`. — nicohvi, Mar 06 '14 at 14:52

score 8 · Answer 1 · edited Feb 18 '16 at 10:07

I monkey patched the log(env, status, header, began_at) function, which is what gets called by rack to produce the apache style logs. We use jruby with logback so we have no use for all the custom logging that seems to pervade the ruby ecosystem. I suspect fishwife is initalizing the CommonLogger, which might explain why all my attempts to disable it or to configure it with a custom logger fail. Probably puma does something similar. I actually had two instances at one point. One logging with my custom logger (yay) and another one still doing its silly puts statements on stderr. I must say, I'm pretty appalled with the logging hacks in the rack ecosystem. Seems somebody needs a big cluebat to their heads.

Anyway, putting this in our config.ru works for us:

module Rack
  class CommonLogger
    def log(env, status, header, began_at)
      # make rack STFU; our logging middleware takes care of this      
    end
  end
end

In addition to that, I wrote my own logging middleware that uses slf4j with a proper MDC so we get more meaningful request logging.

You don't need that. Just launch with `rackup --quiet`. See my answer — Qortex, Apr 10 '20 at 16:06

score 6 · Accepted Answer · answered Mar 06 '14 at 15:24

6

Puma adds logging middleware to your app if you are in development mode and haven’t set the --quiet option.

To stop Puma logging in development, pass the -q or --quiet option on the command line:

puma -p 3001 -q

or if you are using a Puma config file, add quiet to it.

answered Mar 06 '14 at 15:24

matt

78,533
8
163
197

I am using Webrick and I still get logs on STDERR. Weird. – lzap Oct 04 '18 at 11:59

Qortex · Answer 3 · 2020-04-10T17:26:59.343

Rack includes a few middlewares by default when you rackup your application. It is defined in this file.

By default, as you mention, the logging middleware is enabled.

To disable it, just pass the option --quiet to rackup:

rackup --quiet

And the default loggin middleware will not be enabled.

Then, you can enable your own logging middleware without pollution by the default logger (named CommonLogger).

You can also add #\ --quiet to the top of your config.ru file to avoir always typing --quiet, but this behaviour is now deprecated.

score 0 · Answer 4 · answered Oct 04 '18 at 12:13

It's probably not Sinatra what is writing to STDOUT or STDERR, but your webserver. Puma can be started with -q (quiet) option as noted by @matt. When using webrick make sure the AccessLog configuration variable is an empty array, otherwise it will also be logged on your standard output.

Disabling echo from webrick

score 0 · Answer 5 · answered Oct 18 '21 at 23:51

This is one of the top results. So this probably more of a message to my future self the next time I'm annoyed to death about sinatra/puma not shutting up. But to actually get a silent start up:

class MyApp < Sinatra::Base
  configure do
    set :server, :puma
    set :quiet, true
    set :server_settings, Silent: true
  end
end

Disable Rack::CommonLogger without monkey patching

5 Answers5