ody / logger
logging integration for ODY Framework
Requires
- php: >=8.1
- psr/log: ^1.1|^2.0|^3.0
Requires (Dev)
- mockery/mockery: ^1.4
- phpunit/phpunit: ^9.5
- squizlabs/php_codesniffer: ^3.6
This package is auto-updated.
Last update: 2025-03-31 07:41:16 UTC
README
Logging is configured in config/logging.php
and provides various channels for logging:
// Using the logger $logger->info('User logged in', ['id' => $userId]); $logger->error('Failed to process payment', ['order_id' => $orderId]); // Using the logger helper function logger()->info('Processing request');
Custom Loggers in ODY Framework
Creating Custom Loggers
Basic Requirements
All custom loggers must:
- Extend
Ody\Logger\AbstractLogger
- Implement a static
create(array $config)
method - Override the
write(string $level, string $message, array $context = [])
method
Example: Creating a Custom Logger
Here's a simple example of a custom logger that logs to Redis:
<?php namespace App\Logging; use Ody\Logger\AbstractLogger;use Ody\Logger\Formatters\FormatterInterface;use Ody\Logger\Formatters\JsonFormatter;use Ody\Logger\Formatters\LineFormatter;use Psr\Log\LoggerInterface;use Psr\Log\LogLevel;use Redis; class RedisLogger extends AbstractLogger { /** * @var Redis */ protected Redis $redis; /** * @var string */ protected string $channel; /** * Constructor */ public function __construct( Redis $redis, string $channel = 'logs', string $level = LogLevel::DEBUG, ?FormatterInterface $formatter = null ) { parent::__construct($level, $formatter); $this->redis = $redis; $this->channel = $channel; } /** * Create a Redis logger from configuration */ public static function create(array $config): LoggerInterface { // Create Redis connection $redis = new Redis(); $redis->connect( $config['host'] ?? '127.0.0.1', $config['port'] ?? 6379 ); if (isset($config['password'])) { $redis->auth($config['password']); } // Create formatter $formatter = null; if (isset($config['formatter'])) { $formatter = self::createFormatter($config); } // Return new logger instance return new self( $redis, $config['channel'] ?? 'logs', $config['level'] ?? LogLevel::DEBUG, $formatter ); } /** * Create a formatter based on configuration */ protected static function createFormatter(array $config): FormatterInterface { $formatterType = $config['formatter'] ?? 'json'; if ($formatterType === 'line') { return new LineFormatter( $config['format'] ?? null, $config['date_format'] ?? null ); } return new JsonFormatter(); } /** * {@inheritdoc} */ protected function write(string $level, string $message, array $context = []): void { // Format log data $logData = [ 'timestamp' => time(), 'level' => $level, 'message' => $message, 'context' => $context ]; // Publish to Redis channel $this->redis->publish( $this->channel, json_encode($logData) ); } }
The create()
Method
The static create()
method is responsible for instantiating your logger based on configuration:
public static function create(array $config): LoggerInterface { // Create dependencies based on configuration // ... // Return new logger instance return new self(...); }
This method receives the channel configuration from the logging.php
config file and should:
- Create any dependencies the logger needs
- Configure those dependencies based on the config array
- Return a new instance of the logger
The write()
Method
The write()
method is where the actual logging happens:
protected function write(string $level, string $message, array $context = []): void { // Implement logging logic here }
This method is called by the parent AbstractLogger
class when a log message needs to be written. It receives:
$level
: The log level (debug, info, warning, etc.)$message
: The formatted log message$context
: Additional context data
Using Custom Loggers
Method 1: Configuration-Based Discovery
The simplest way to use a custom logger is to specify the fully-qualified class name in your logging configuration:
// In config/logging.php 'channels' => [ 'redis' => [ 'driver' => 'redis', 'class' => \App\Logging\RedisLogger::class, 'host' => env('REDIS_HOST', '127.0.0.1'), 'port' => env('REDIS_PORT', 6379), 'channel' => 'application_logs', 'level' => 'debug', ], ]
When you specify a class
parameter, that class will be used regardless of the driver name.
Method 2: Driver Name Registration
You can register your logger with a driver name, which allows you to reference it using just the driver name:
// In a service provider's register method $this->app->make(\Ody\Logger\LogManager::class) ->registerDriver('redis', \App\Logging\RedisLogger::class);
Then in your configuration:
// In config/logging.php 'channels' => [ 'redis' => [ 'driver' => 'redis', // This will use the registered RedisLogger 'host' => env('REDIS_HOST', '127.0.0.1'), 'port' => env('REDIS_PORT', 6379), 'channel' => 'application_logs', 'level' => 'debug', ], ]
Method 3: Automatic Discovery
If your logger follows the naming convention {Driver}Logger
and is in one of the registered namespaces, it will be discovered automatically:
// In config/logging.php 'channels' => [ 'redis' => [ 'driver' => 'redis', // Will look for RedisLogger // Configuration... ], ]
The framework will search for RedisLogger
in the registered namespaces (\Ody\Logger\
and \App\Logging\
by default).
Creating Custom Formatters
If the standard formatters don't meet your needs, you can create your own by implementing the FormatterInterface
:
namespace App\Logging; use Ody\Logger\Formatters\FormatterInterface; class CustomFormatter implements FormatterInterface { public function format(string $level, string $message, array $context = []): string { // Custom formatting logic return "[$level] $message " . json_encode($context); } }
Complete Example: Using Redis Logger
Configuration
// In config/logging.php 'channels' => [ // Using explicit class 'redis' => [ 'driver' => 'redis', 'class' => \App\Logging\RedisLogger::class, 'host' => env('REDIS_HOST', '127.0.0.1'), 'port' => env('REDIS_PORT', 6379), 'password' => env('REDIS_PASSWORD', null), 'channel' => 'app_logs', 'formatter' => 'json', 'level' => 'debug', ], // Using it in a stack 'production' => [ 'driver' => 'group', 'channels' => ['file', 'redis'], ], ],
Usage
// Send to redis channel logger('User registered', ['id' => 123], 'redis'); // Or use the stack logger('API request processed', ['endpoint' => '/users']);
With this system, you can create custom loggers that integrate seamlessly with the ODY Framework logging infrastructure.