Why are we rebuilding Monolog?
Was wondering, when looking through the logging manual, and seeing the feature requests, it just seems Monolog is being copied?
Why not implement Monolog like many others did? It has support for many features requested and connects with the most common systems.
Symfony2 comes out of the box with Monolog.
Silex comes out of the box with Monolog.
Laravel 4 comes out of the box with Monolog.
PPI comes out of the box with Monolog.
CakePHP is usable with Monolog via the cakephp-monolog plugin.
Slim is usable with Monolog via the Slim-Monolog log writer.
XOOPS 2.6 comes out of the box with Monolog.
Aura.Web_Project comes out of the box with Monolog.
Updated by Steffen Müller almost 8 years ago
This is a valid question. The only answers I have are: historical reasons and better integration into TYPO3 core, especially extensibility and configuration.
If you feel like replacing the current Logging API with Monolog, then go ahead and contact the core team/active contributor. I don't have time for this task. However I would support the idea.
This request is not valid for 6.2 since it already has reached feature freeze phase.