6c2cf494b5
- Include all necessary classes in `dependencies.config.php` - Add DI-reference to BaseObject (acts as a global registry) - Refactor all static "init()" methods to use the global registry - Refactor Logging for Worker-Logger a little bit |
||
|---|---|---|
| .. | ||
| Monolog | ||
| AbstractLogger.php | ||
| ProfilerLogger.php | ||
| README.md | ||
| StreamLogger.php | ||
| SyslogLogger.php | ||
| VoidLogger.php | ||
| WorkerLogger.php | ||
Friendica\Util\Logger
This namespace contains the different implementations of a Logger.
Configuration guideline
The following settings are possible for logger_config:
monolog: A Logging framework with lots of additions (see Monolog). There are just Friendica additions inside the Monolog directorystream: A small logger for files or streamssyslog: Prints the logging output into the syslog
VoidLogger is a fallback logger without any function if no debugging is enabled.
ProfilerLogger is a wrapper around an existing logger in case profiling is enabled for Friendica.
Every log call will be saved to the Profiler with a timestamp.
Implementation guideline
Each logging implementation should pe capable of printing at least the following information:
- An unique ID for each Request/Call
- The process ID (PID)
- A timestamp of the logging entry
- The critically of the log entry
- A log message
- A context of the log message (f.e which user)
If possible, a Logger should extend AbstractLogger, because it contains additional, Friendica specific business logic for each logging call.