Friendica Communications Platform (please note that this is a clone of the repository at github, issues are handled there)
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
nupplaPhil 800694e9b3
Remove unused `use` statements & remove PConfig class
2 years ago
Monolog Rename & Testfix 2 years ago
AbstractLogger.php Rename & Testfix 2 years ago
ProfilerLogger.php Added StreamLogger and ProfilerLogger 2 years ago Rename & Testfix 2 years ago
StreamLogger.php Add timezone information to logger timestamp 2 years ago
SyslogLogger.php Remove extra spaces before closing parentheses in src/ 2 years ago
VoidLogger.php Syslog - Disabling 2 years ago
WorkerLogger.php Remove DependencyFactory 2 years ago


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 directory
  • stream: A small logger for files or streams
  • syslog: 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.