- Is nti/log-bundle a Laravel package?
- No. nti/log-bundle is a Symfony bundle, not a Laravel package: it contains a Bundle class, DependencyInjection extension, service definitions, and framework lifecycle hooks that Laravel does not provide. Laravel developers should treat it as a Symfony component to port or borrow from, not a drop-in Composer package.
- Can I install nti/log-bundle in a Laravel app with Composer?
- Composer may install it, but Laravel will not auto-register the bundle or apply its Monolog configuration. You would need to translate the bundle's channels, handlers, and levels into config/logging.php or a custom service provider that registers Monolog handlers. For most Laravel apps that is more work than configuring logging directly.
- What does nti/log-bundle actually do?
- It wraps Monolog configuration into a reusable package with preconfigured handlers for files, console, and custom targets. It also exposes configurable log levels and channels, request/response and exception logging helpers, and a PSR-3 compatible logger service. The goal is standardized log output without repeating boilerplate in every services.yaml.
- Which version of nti/log-bundle should I evaluate or fork?
- Evaluate or fork from v3.0.0, not from main. That release includes fixes for the event subscriber folder deprecation and entity manager inclusion, and it migrates Doctrine mapping from annotations to attributes. The assessment treats the major-version bump as a breaking change, so annotation-based consumers cannot assume support.
- Does nti/log-bundle work with Laravel and Eloquent?
- Feasibility is near zero for a Laravel plus Eloquent target. Eloquent apps do not use the Doctrine event listeners or entity manager that v3.0.0 modernizes, and Laravel already ships Monolog with its own logging configuration. You would be adopting a Symfony bundle for functionality Laravel largely provides natively.
- What license and copyright terms apply to nti/log-bundle?
- The declared license and copyright owner are not confirmed in the provided material, and the assessment flags LICENSE/IP as the first gate before committing engineering time. Check the repository LICENSE file and confirm the copyright holder before using it commercially. Do not assume a permissive license just because the package is public.
- Is nti/log-bundle actively maintained and tested?
- The package has zero stars, zero dependents, and no third-party smoke test or issue traffic. v3.0.0 is a weak but real liveness signal because it tracks upstream Symfony and Doctrine deprecations, but there is no changelog or test report confirming the fixes work outside the author's environment. Treat it as unvalidated and budget time for your own smoke tests.
- What PHP, Symfony, and Doctrine versions does nti/log-bundle v3.0.0 require?
- Exact constraints are not confirmed in the provided material. The annotation-to-attribute migration implies PHP 8.0 or later and a Doctrine ORM version that supports attribute mapping, likely ORM 2.9+ or 3.x. Read composer.json for the exact constraints on php, symfony/*, doctrine/orm, and doctrine/dbal, and check whether the annotation driver is dropped or still a fallback.
- Is nti/log-bundle safe for production logging, including PII?
- Proceed carefully. The bundle is not externally validated and pulls in transitive symfony/* packages, so review the dependency tree and pin versions. Doctrine listener logging can capture change sets and SQL parameters, which creates a PII exposure risk if those logs reach shared storage. Redact sensitive fields and verify handler targets before production use.
- How do I configure log channels and levels in nti/log-bundle, and what are the alternatives?
- In Symfony you configure channels, levels, and handlers through the bundle configuration, not Laravel's config/logging.php. For Laravel, the practical alternative is built-in Monolog channels such as stack, daily, and slack, plus a small custom listener if you need Doctrine event logging. If you want this bundle's conventions, fork v3.0.0 rather than depending on it directly.