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.
I know I could create custom log levels, but I think a logger is such internal part of framework, that it is actually establishing the culture of programming in that framework. And for symfony, as the profi framework, I would expect to create the culture of "use logger properly and distinguish properly between various kinds of errors" So for me, I would prefer to not change what is working fine, and keep the levels as they are in symfony 1.4 or Zend. Peter On 21 dub, 18:21, Georg <[email protected]> wrote: > Am 21.04.2011 12:47, schrieb Johannes Schmitt: > > > For the method names, I think they need to be viewed in combination with > > the variable they are called on, e.g. > > > $logger->log() vs. $logger->addRecord() > > $logger->debug() vs. $logger->addDebug() > > etc. > > Personally I would prefer > > $log->addWarning() > > over > > $log->warning() > > because I feel the object I am using is a log and not a logger (even if > it is the logger which is doing the work) -- 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
