[RFC] logger/logging

[Nicofuma]

Ticket: PHPBB3-13714
PR:
--------------------

Current state

Currently we use a logger which i completely bound to phpBB, which leads to a few issue:

• It's completely incompatible with third party
• It's not really extensible

but it also has some nice features like:

• the ability to filter the log
• the ability to give limited access to the logs depending on the acl system.

there is also some other feature that, I think, shouldn't exists like:

• The ability to delete all or part of the logs, I think that it should be done by a cron job and nothing else (ie: just automatic purge) or at least with a special admin permission

Proposal

1. Our logger must be PSR3 compatible
2. Use an interface to be able to change the logger
3. Use Monolog if available and backport the Symfony Monolog Bridge and Bundle (their integration is pretty good: they use Monolog and its features if available, but their still able to use any logger which implements their interface without having to change anything else than the definition of the logger service)
4. Use a custom handler to store some entries (or all of them I don't know?) in the database (mainly what is currently logged) and so keep our abilities to display and filter the logs
5. Improve the current UI to add the severity
6. Write all the logs in a file and rotate them (ie: one file per day) by default, they will be written in the board default language
7. Use the DI and a config file (DI extension) to manage all the configuration, so the board admin will be completely able to configure the logging
8. Add a viewer for the log files in the acp?

[rfdy]

We're also interested in this feature. Currently our extensions add entries to the log, but displaying the data back is difficult without events being triggered to alter the display row.

Ideally there would be a mechanism for extensions to define new log types and attach handlers for displaying/managing them.

[Pony99CA]

While improved logging would be great, I have no idea what "PSR3" or "DI" mean.

The admin should also be able to turn on or off other items to log (specifically user logins/logouts and guest visits, but possibly other items).

Steve

[Nicofuma]

DI means Dependency Injection, and PSR3 is a standard for the logging edited by the php-fig group (http://www.php-fig.org/psr/psr-3/)

[Pony99CA]

DI means Dependency Injection, and PSR3 is a standard for the logging edited by the php-fig group (http://www.php-fig.org/psr/psr-3/)

Thanks for the clarification. To be honest, I'm still not sure what "dependency injection" is, but I can Google that if I want to learn more.

Steve