Model-specific SQL logging in rails

Question

In my rails application, I have a background process runner, model name Worker, that checks for new tasks to run every 10 seconds. This check generates two SQL queries each time - one to look for new jobs, one to delete old completed ones.

The problem with this - the main log file gets spammed for each of those queries.

Can I direct the SQL queries spawned by the Worker model into a separate log file, or at least silence them? Overwriting Worker.logger does not work - it redirects only the messages that explicitly call logger.debug("something").

Adam Byrtek · Accepted Answer · 2009-07-24 23:54:31Z

4

The simplest and most idiomatic solution

logger.silence do
  do_something
end

See Logger#silence

answered Jul 24, 2009 at 23:54

Adam Byrtek

12.2k2 gold badges35 silver badges33 bronze badges

Sign up to request clarification or add additional context in comments.

1 Comment

Toms Mikoss Over a year ago

Ended up doing this. Not what I had hoped for, but it does solve the problem.

Community · Accepted Answer · 2017-05-23 12:07:04Z

0

Queries are logged at Adapter level as I demonstrated here. How do I get the last SQL query performed by ActiveRecord in Ruby on Rails?

You can't change the behavior unless tweaking the Adapter behavior with some really really horrible hacks.

edited May 23, 2017 at 12:07

CommunityBot

11 silver badge

answered Jul 24, 2009 at 16:24

Simone Carletti

177k50 gold badges371 silver badges370 bronze badges

Comments

François Beausoleil · Accepted Answer · 2009-07-24 23:08:09Z

0

class Worker < ActiveRecord::Base
  def run
    old_level, self.class.logger.level = self.class.logger.level, Logger::WARN

    run_outstanding_jobs
    remove_obsolete_jobs
  ensure
    self.class.logger.level = old_level
  end
end

This is a fairly familiar idiom. I've seen it many times, in different situations. Of course, if you didn't know that ActiveRecord::Base.logger can be changed like that, it would have been hard to guess.

One caveat of this solution: this changes the logger level for all of ActiveRecord, ActionController, ActionView, ActionMailer and ActiveResource. This is because there is a single Logger instance shared by all modules.

answered Jul 24, 2009 at 23:08

François Beausoleil

16.6k11 gold badges71 silver badges97 bronze badges

Collectives™ on Stack Overflow

Model-specific SQL logging in rails

3 Answers 3

1 Comment

Comments

Comments

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

3 Answers 3

1 Comment

Comments

Comments

Your Answer

Sign up or log in

Post as a guest

Linked

Related