Weave Code
Easy Log Bundle Laravel Package
systemsdk/easy-log-bundle
EasyLogBundle is a Symfony bundle that simplifies application logging with configurable channels, handlers, and structured output. Capture errors and events, attach useful context, and manage PSR-3-compatible logs with minimal setup for development and production.
At a glance
Frequently asked questions about Easy Log Bundle
- Does systemsdk/easy-log-bundle work with Laravel?
- It is a Symfony bundle, not a Laravel package. Laravel consumes Symfony components such as HttpFoundation and Console but does not use the Symfony bundle system, so there is no service provider or config publishing path documented here. Before adopting it, confirm whether the package ships a Laravel bridge or is Symfony-first only. If it is Symfony-first, you would have to write your own integration layer.
- How do I install systemsdk/easy-log-bundle?
- Install it with Composer and register the bundle in your Symfony kernel bundles list, then publish or write the bundle configuration for your channels and handlers. For Laravel projects there is no documented vendor:publish config stub, because Laravel's config publishing is a Laravel concept the bundle does not use. Run composer why-not systemsdk/easy-log-bundle with your target version first to see whether any constraint blocks the install.
- Which PHP and Symfony versions does easy-log-bundle support?
- The v2.1.0 changelog only states that bundle configuration was improved for the latest Symfony framework, so the exact PHP and Symfony floors are not published in the release note. Check the composer.json constraints for the symfony/* requirements before upgrading. That matters for Laravel because Laravel pins Symfony components per major version, so a raised Symfony floor can silently raise your minimum Laravel version.
- Is systemsdk/easy-log-bundle a replacement for Monolog?
- No, it is built on the familiar PSR-3 and Monolog logging stack rather than replacing it. The bundle contributes sensible defaults, configurable channels and structured context on top of the handlers you already know. It is described as working alongside existing Symfony logging, so you can keep your current Monolog setup in place.
- Can I use easy-log-bundle with Laravel's existing Monolog channels?
- Anything that speaks PSR-3 can in principle share a Monolog logger, and this bundle targets PSR-3. In practice, Laravel builds and configures its logger through its own logging manager, so the bundle's bundle-extension configuration would not be wired automatically. You would need a small bridge that registers the bundle's services or reads its configuration manually.
- What changed in easy-log-bundle v2.1.0 and is it a breaking change?
- The entire changelog entry is improved bundle configuration for the latest Symfony framework. By semver convention a minor release is additive and backward compatible, so no breaking change or deprecation is declared. Treat that as a low-information note rather than proof that nothing moved, and verify config keys yourself.
- Did easy-log-bundle v2.1.0 raise its minimum Symfony version?
- The wording about the latest Symfony framework strongly suggests the symfony/* floor moved, but the release note does not confirm it. Run composer update --dry-run in a representative service to see the dependency delta before committing. If the floor did rise, the real risk is a cascading minimum Laravel version rather than runtime behaviour.
- How do I configure log levels, channels and context in easy-log-bundle?
- Configuration is done through the bundle extension, where you set log levels, channels and the context attached to entries. The v2.1.0 note mentions improved bundle configuration, and improvements of that kind often mean restructured or renamed keys. If keys changed, a previously published config file will not be overwritten automatically, so diff your config against the new defaults.
- Is easy-log-bundle safe to run in production?
- The change itself is low risk at runtime, since a config-only minor release rarely alters execution paths. The production hazard is silent misconfiguration: a renamed config key can leave a deployed app on a stale stub that passes CI and only surfaces under real traffic. Deploy to a staging environment and compare emitted log entries against your expected channels before rolling out.
- Is systemsdk/easy-log-bundle actively maintained and what are the alternatives?
- The repository ships a v2.1.x line, but the changelog gives no support policy, so ask whether 2.1.x is the maintained branch and how long 2.0.x is supported. If you need a Laravel-native path, Monolog with Laravel's own channel configuration or a dedicated Laravel logging package will be a better fit. Keep this bundle for Symfony services where bundle configuration is the real integration surface.
Weaver
How can I help you explore Laravel packages today?