On Thu, 6 Oct 2011, Jim Jagielski wrote:
On Oct 5, 2011, at 7:07 PM, Daniel Ruggeri wrote:
On 10/5/2011 4:18 PM, Stefan Fritsch wrote:
True. But a generic apparatus for even more fine-grained log
configuration won't happen in time for 2.4.
I have toyed with the idea of this... do you have suggestions on how
this might be implemented?
I have thought about adding logging subsections for each module, which
could then be configured separately (like core.client_error:crit ). But I
then dropped the idea because it would involve lots of complexity that
would then only be used by 2-3 modules.
One of the ideas I heard (or thought of -
don't recall) was to implement an error log filter such that messages
matching a certain regex get dropped. To me that seems like it would be
very expensive for busier sites, but would serve the purpose for some of
the user base.
It would be quite expensive to be sure… for some sites, logging
is the most expensive part of the server.
But regex matches are usually cheaper than logging to disk (especially
considering the increasing number of CPU cores). So it may have some uses
if a significant number of messages is filtered out.
