Hi Tom,
Not sure if it applies to your specific case, but whenever I come
across the need to quiet the logging activity for some particular
verbose-under-normal-logging activity process that I'm really only
concerned about logging-wise only if it fails, ... I usually just
temporarily up the log-level for the specific handling of that
process. Something like:
# in the controller:
...
bak_log_level = logger.level
begin
logger.level = Logger::ERROR
# do some stuff ...
...
ensure
logger.level = bak_log_level
end
...
Jeff
On Apr 27, 3:49 pm, TomRossi7 <t...@themolehill.com> wrote:
> Marnen,
>
> I do appreciate the feedback, but I wonder if others agree? Maybe
> that is why its not a simple task within Rails?
>
> Anyone?
>
> Thanks,
> Tom
>
> On Apr 27, 5:08 pm, Marnen Laibow-Koser <li...@ruby-forum.com> wrote:
>
>
>
>
>
> > TomRossi7 wrote:
> > > I have an action being called by a monitoring service.
>
> > > Leaving this out of the log is not "inaccurate",
>
> > I'm not sure I agree. The log tells you what Rails has been up to. One
> > of the things it has been up to is servicing the requests that come from
> > the monitoring service. Leaving those requests out of the log will
> > lessen the utility of the log.
>
> > Consider: if there were a bug or bottleneck in the monitoring request,
> > how would you know? If the monitoring service weren't requesting its
> > action, how would you know?
>
> > Picking and choosing in the log is a bad idea.
>
> > > anymore than not
> > > logging static files referenced is the public folder is "inaccurate".
>
> > The analogy doesn't hold. The log is specifically a Rails log. Files
> > in /public aren't served by Rails; therefore, they don't appear in the
> > log. Your monitoring requests, however, are served by Rails and should
> > appear in the log.
>
> > > Thanks,
> > > Tom
>
> > Best,
> > --
> > Marnen Laibow-Koserhttp://www.marnen.org
> > mar...@marnen.org
> > --
> > Posted viahttp://www.ruby-forum.com/.
>
> > --
> > You received this message because you are subscribed to the Google Groups
> > "Ruby on Rails: Talk" group.
> > To post to this group, send email to rubyonrails-t...@googlegroups.com.
> > To unsubscribe from this group, send email to
> > rubyonrails-talk+unsubscr...@googlegroups.com.
> > For more options, visit this group
> > athttp://groups.google.com/group/rubyonrails-talk?hl=en.
>
> --
> You received this message because you are subscribed to the Google Groups
> "Ruby on Rails: Talk" group.
> To post to this group, send email to rubyonrails-t...@googlegroups.com.
> To unsubscribe from this group, send email to
> rubyonrails-talk+unsubscr...@googlegroups.com.
> For more options, visit this group
> athttp://groups.google.com/group/rubyonrails-talk?hl=en.
--
You received this message because you are subscribed to the Google Groups "Ruby
on Rails: Talk" group.
To post to this group, send email to rubyonrails-t...@googlegroups.com.
To unsubscribe from this group, send email to
rubyonrails-talk+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/rubyonrails-talk?hl=en.
