Weave Code
Logger Extra Bundle Laravel Package
playtini/logger-extra-bundle
A Symfony bundle that extends Monolog with extra logging context and integrations, making it easier to capture request, user, and environment details for more consistent, searchable application logs. Useful for debugging and production observability.
🐈 Add logs extra info
Frequently asked questions about Logger Extra Bundle
- Is playtini/logger-extra-bundle compatible with Laravel?
- No, playtini/logger-extra-bundle is a Symfony bundle, not a Laravel package. It integrates through Symfony's service container and bundle configuration, so it cannot be installed and enabled in Laravel the same way. Laravel developers can still borrow the processor ideas, but the package itself targets Symfony applications.
- How do I install playtini/logger-extra-bundle?
- Install it with Composer using composer require playtini/logger-extra-bundle. In a Symfony app, enable the bundle in config/bundles.php and configure the processors or services you need. Check Packagist and the repository for the exact supported Symfony and PHP versions before installing.
- What Monolog processors does this bundle provide?
- It provides reusable Monolog processors for request context, response context, and environment details. These processors enrich each log record with application-aware metadata instead of requiring custom handlers in every project. The result is more consistent, searchable logs with less per-project wiring.
- How does correlation ID tracing work with this bundle?
- The bundle supports correlation IDs by attaching a shared identifier to log records as they are processed. That lets you trace a single request or operation across multiple services and log entries. You typically populate the ID from an incoming header or generate one at the edge of your application.
- Can I use this bundle with Laravel's Monolog stack?
- Not directly, because the package is built as a Symfony bundle with Symfony container integration. Laravel also uses Monolog, so you could adapt similar processor logic into a custom Laravel logging tap or Monolog processor. That would be a manual port rather than native package support.
- Which Symfony versions does playtini/logger-extra-bundle support?
- The repository's composer.json and Packagist metadata are the authoritative source for supported Symfony and PHP versions. Support can change between releases, so check the version constraints before adding it to an existing project. The README may not list every compatible version.
- How do I configure the bundle in Symfony?
- Enable the bundle in config/bundles.php and configure it through Symfony's service container and bundle configuration. You register the processors you want and let Symfony wire them into Monolog. The bundle is designed to keep that setup lightweight and reusable across applications.
- Does this bundle add much overhead in production?
- The bundle is designed around lightweight Monolog processors that add context to log records rather than replace Monolog. Production impact depends on how many processors you enable and how much request or response data you capture. Review what you attach and avoid logging sensitive or excessively large payloads.
- How do I test logs enriched by playtini/logger-extra-bundle?
- Test the enriched records with a Monolog test handler and assert that the expected request, response, environment, or correlation ID context is present. In Symfony, you can also verify that the processors are wired through the container. If you adapt the processors for Laravel, test them through Laravel's logging stack with a custom handler.
- What are Laravel alternatives to playtini/logger-extra-bundle?
- In Laravel, start with built-in logging context through Log::withContext and custom Monolog processors, which cover much of the same request and correlation ID use case. Packages such as Sentry or Flare add observability and error tracking, while Spatie packages help with structured logging and activity records. For a Symfony-style port, write a small Laravel logging tap or Monolog processor rather than installing this bundle.
Weaver
How can I help you explore Laravel packages today?