Feedbacks/issues of Zend_Log for ZF1
- More flexible mapping ror Zend_Log_Writer_Db ZF-2658
- Zend_Log_Formatter_Simple must print %info% event ZF-10427
- Incorrect handling of E_DEPRECATED and E_USER_DEPRECATED ZF-12031
- Patch to make line and file information available in log events ZF-2428
- Add Zend_Log::getWriters() to return list of attached writers ZF-3581
- Create the log file only if there is something to log ZF-5741
- Add callback support for log events ZF-7959
- Filtering messages which are not strings ZF-5778
- Methods to remove log writers, filters and event items. ZF-1833
Feddbacks/issues of Zend\Log for ZF2
- Array arguments get flattened when creating Zend\Log\Logger ZF2-34
- Reflection is used in Zend_Log::__construct() to build priorities name (slow)
- Magic method __call() used for shortcut log an event (slow, and hard to discover API)
- Bad design for Zend_Log::factory() (it calls others factories of writer/formatter/filter defined in config)
Proposals
- API discoverable (emerg, alert, crit, err, warn, notice, info, debug)
- Improve Simple Formatter (according to the feedbacks/issues)
- Use the plugin broker to review factory (Zend\Loader\Broker, Zend\Loader\Pluggable)
- Use of SplPriorityQueue to manage multiple writers (with priorities)
- Refactor Zend\Log\Filter\Message using Zend\Validator (included the ValidatorChain)
- New formatter (json)
- Add a Zend\Log\Filter\Validator to use a Zend\Validator object like "filter" for the log message
- Create LoggerAware for Di
- Renderer for exceptions, array, string object, event, etc (format exception instead of __toString())
- Modify parameters of Logger::log($priority, $message, $extras)
- Rename Filter\Message in Filter\StringMatch or Filter\Regex
Usage
Labels:
None