Tracy has been set as a default error/exception logger #416

[fedys]

ErrorLogger has been completely removed with its related classes/configs
Tracy also includes an Exception markup as an attachment

[coveralls]

Coverage increased (+0.3%) to 37.799% when pulling fa8041c on fedys:issue/416 into c4ec29f on cross-solution:feature/ZF3.

[fedys]

I tested the following scenarios:

• production HTTP: notice, exception & fatal
• production CLI: notice, exception & fatal
• development HTTP: notice, exception & fatal
• development CLI: notice, exception & fatal

I am not 100% sure about removed classes/configuration. I assume they are all related with the old ErrorLogger. Please check the removals carefully.

Consider the following idea. Create a single "System" logger which would replace multiple 'Core/Log' & 'Log/Core/Mail' loggers. This logger would have several writers attached. These writer would log messages into different locations depending of a message severity. For example, all messages would be written into yawik.log, severity above 'error' would be written into error.log and also send via Tracy email.

[TiSiE]

I don't grasp why we would need such a "System Logger", when tracy DOES log automatically into specific files in its log directory (as I understand). Don't get me wrong, such a Logger would be fancy indeed..

[fedys]

@TiSiE See the following example where the System logger could be used to log to file and send email.

YAWIK/module/Auth/src/Auth/Controller/RegisterConfirmationController.php

Line 53 in dee413c

$this->logger->crit($e);

[fedys]

@TiSiE In other words, the System logger could be used in cases when something unexpected happens but you do not want to let the application crash.

[TiSiE]

@fedys I see. We should keep that idea around!