On Fri, Apr 22, 2011 at 11:18 PM, PeTe <[email protected]> wrote: > In our company, we are using an email logger, which immediately alerts > us, when an error of an ALERT level occurs. Log level CRIT is for > unusable parts of system and EMERG (from ZF) is for "database not > found" kind of error - complete unusability of the system. If we only > had ERROR as the highest level, we would always be notified by email > about all kinds of 404 errors basically. I don't find it sufficient to > have ERROR as the highest level. At least ALERT and CRIT are important > for us. I don't see much difference between NOTICE and INFO, so if one > of them is gone, it doesn't matter.
Interesting - all I was looking for was a use case. I agree that the 404 problem is real. I don't want to set up a mail alert on errors and get spammed by crawlers trying to find vulnerabilities. Maybe we should bring down the 4xx to warning level, or raise the other "real" errors to something above error. Either way, I'll give it some thought and probably add some more levels to Monolog. As for the method naming. I guess the opinion is too mixed to justify the BC break at this point, so I'll let it be. Both ways are supported by Monolog anyway, but Sf2 core interfaces will remain as they are. Cheers -- Jordi Boggiano @seldaek :: http://seld.be/ -- If you want to report a vulnerability issue on symfony, please send it to security at symfony-project.com You received this message because you are subscribed to the Google Groups "symfony developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/symfony-devs?hl=en
