Weave Code
Logger Extra Bundle Laravel Package
silpion/logger-extra-bundle
Symfony bundle that extends Monolog logging with practical extras: additional processors and configuration to enrich log records with useful context, simplify setup, and make application logs easier to inspect and route. Integrates via standard Symfony service configuration.
Extra logging features for Monolog in a Symfony2 bundle.
Frequently asked questions about Logger Extra Bundle
- Is silpion/logger-extra-bundle compatible with Laravel?
- No. It is a Symfony2 bundle built around AppKernel registration, Symfony's dependency injection container, and bundle configuration, none of which exist in Laravel. Laravel and Symfony both use Monolog, so only isolated Monolog processors could be portable, not the bundle itself. Treat it as a reference implementation rather than a Laravel dependency.
- Can I install silpion/logger-extra-bundle in a Laravel app with Composer?
- You should not install it as a runtime dependency. It would pull Symfony2-era components that can conflict with the modern Symfony packages Laravel already depends on, and the bundle will not boot without Symfony's bundle system. Even if Composer resolves the package, the integration wiring will not work in a Laravel application. Port the logging behavior instead.
- What does silpion/logger-extra-bundle do?
- It is a Symfony bundle that extends Monolog logging by adding processors which attach the authenticated user and security token data to log records. It is designed to integrate with standard monolog configuration and provide consistent extra fields across handlers and channels. Its value in a Laravel context is the logging behavior, not the Symfony bundle wiring.
- How do I configure silpion/logger-extra-bundle in Laravel?
- You cannot configure it through Laravel's config/logging.php or service provider model. The bundle expects Symfony bundle registration and its own configuration tree, which Laravel does not provide. The equivalent setup is to register a Monolog processor or logging tap on your Laravel channels.
- Which Laravel and PHP versions does silpion/logger-extra-bundle support?
- None are officially supported for Laravel. The last release was in 2014 and targeted PHP 5.x and Symfony 2.x, so there is no declared compatibility with Laravel 8, 9, 10, 11, or 12. Modern Laravel versions require supported PHP releases and current Monolog, which this abandoned package does not address.
- Does silpion/logger-extra-bundle work with Monolog 2 or Monolog 3?
- You should assume it does not. The bundle was released against Monolog 1.x-era APIs and Symfony2 service definitions, and no updates have been published since 2014. Monolog 2 and 3 changed processor interfaces and handler signatures, so copied code may fail. Any reuse requires reviewing and updating the processor classes.
- Can I reuse its Monolog processors in Laravel?
- Only if the processor classes are pure Monolog code with no Symfony container, event dispatcher, or security-token dependencies. Audit each class, remove Symfony-specific constructor arguments, and bind the logic to Laravel's Auth and request context. Most bundles of this age mix Monolog code with Symfony services, so expect a small port rather than drop-in reuse.
- Is silpion/logger-extra-bundle maintained and safe for production?
- It is abandoned and unmaintained, with no PHP 8 or modern Monolog compatibility updates and no security patching. Running it in production creates reliability and security exposure, including possible fatal errors or silent log loss. The MIT license makes source reuse legal, but production use should be limited to a reviewed and tested port.
- What alternatives should Laravel developers use for user-aware logging?
- Laravel's native Log::withContext(), custom Monolog processors, middleware, and channel taps cover most user and request enrichment needs. Maintained packages for correlation IDs, request logging, and structured logging are safer than a 2014 Symfony bundle. For GELF, Logstash, or JSON output, choose a maintained Monolog handler or a Laravel channel driver.
- How do I port and test the bundle's logging behavior in Laravel?
- Audit the bundle for processors, handlers, formatters, and event subscribers, then classify each as portable Monolog code or Symfony-coupled code. Reimplement the minimal behavior as a Laravel logging tap, Monolog processor, or middleware, register it in config/logging.php, and cover it with tests. In PHPUnit, push a record through a Monolog logger with your processor and assert that the expected user and request fields appear in the extra array.
Weaver
How can I help you explore Laravel packages today?