Weave Code
Monolog Bridge Laravel Package
symfony/monolog-bridge
Symfony Monolog Bridge integrates the Monolog logging library with Symfony components, providing handlers and processors for console, HTTP kernel, security, and mailer so you can route framework logs into Monolog channels cleanly.
Provides integration for Monolog with various Symfony components
Frequently asked questions about Monolog Bridge
- How do I install symfony/monolog-bridge in a Laravel application?
- Install it with composer require symfony/monolog-bridge, but let Composer resolve a bridge version that matches your Laravel app's Monolog constraint. Laravel 9 and 10+ commonly use Monolog 3.x, so do not force the 5.4 bridge line onto those apps. After installation, wire the desired Symfony handlers or processors into a Laravel logging channel or push them onto the underlying Monolog logger. Test the channel with an Artisan command or queue worker before production.
- Does symfony/monolog-bridge support Laravel 10 or Laravel 11?
- It is a Symfony package rather than a Laravel-specific package, so support depends on PHP, Symfony, and Monolog constraints rather than a declared Laravel version. Modern Laravel releases typically use Monolog 3.x, which requires a matching newer bridge line, not the 5.4 branch. Check Composer resolution and run your logging tests on the target Laravel version before deploying.
- Is symfony/monolog-bridge compatible with Monolog 3?
- Yes, but only on the bridge version line built for Monolog 3, such as the newer 6.4, 7.x, or 8.x lines. The 5.4 branch targets Monolog 1.x and 2.x, so forcing it into a Monolog 3 Laravel app is a downgrade risk. Confirm the exact bridge and Monolog constraints with Composer before upgrading.
- What does the symfony/monolog-bridge 5.4.54 security release fix?
- Version 5.4.54 contains a terminal-escaping fix described as Escape context strings written to the terminal (#65692). It addresses Monolog context values being rendered raw to a terminal or terminal-like consumer, where ANSI or control sequences could spoof or corrupt log output. The risk is higher when context includes untrusted data such as request headers, user agents, or exception messages. The release notes do not include a CVE, so check the Symfony advisory for details.
- Should I upgrade to symfony/monolog-bridge 5.4.54 in Laravel?
- Upgrade to 5.4.54 or later if your application is on the 5.4 bridge line and Monolog 1.x or 2.x. If your Laravel app uses Monolog 3.x or a newer bridge line, do not downgrade to 5.4 just to consume this patch; confirm that the equivalent fix is present in your line. Treat an 8.1.0-BETA3 deployment as beta risk and verify advisory coverage before relying on it.
- How do I use Symfony Monolog handlers and processors in Laravel logging channels?
- Laravel configures logging through channels in config/logging.php and builds on Monolog underneath. You can add Symfony bridge handlers or processors by customizing a channel, registering a custom logger, or pushing handlers and processors onto the Monolog logger after resolution. Because Laravel's container is not Symfony DependencyInjection, expect to bind dependencies manually or wrap Symfony services behind Laravel facades. Keep configuration explicit and test each channel's formatter and output target.
- Can I use Symfony ErrorLogger with Laravel's exception handling?
- Symfony ErrorLogger can be an option, but it carries integration and conflict risk in Laravel. Laravel has its own exception handler, and Debugbar or Whoops-style handlers may compete for the same errors. If you use it, bind it manually, avoid duplicate reporting, and verify behavior in console, HTTP, and queue contexts. For most Laravel apps, the native exception logging path is simpler.
- How should I test symfony/monolog-bridge integration in a Laravel app?
- Test the bridge at the handler and processor level by instantiating them directly and asserting the resulting Monolog records, for example with Monolog's TestHandler. Also exercise the real Laravel path through an Artisan command, queue worker, or stderr channel that renders context to a terminal-like consumer. Include malicious context containing ANSI or control characters to confirm escaping and sanitization. Run these tests on the exact Laravel, Monolog, and bridge versions you deploy.
- What are alternatives to symfony/monolog-bridge for Laravel logging?
- Laravel's built-in logging channels already use Monolog and cover many common needs without extra bridge code. You can also use Monolog handlers and processors directly, write custom Laravel processors, or choose Laravel-focused logging packages for destinations such as Slack, Papertrail, or other services. The Symfony bridge is most useful when you specifically need its Symfony component handlers, processors, or error-logging integrations.
- Is symfony/monolog-bridge maintained and safe for production Laravel apps?
- Symfony maintains the package and ships security releases, so production safety depends on staying on a supported line that matches your Laravel app's Monolog version. Use the latest patched release for your line, and do not mix the 5.4 bridge with Monolog 3. Add defense-in-depth by stripping ANSI and control characters from untrusted context before terminal rendering, especially in Artisan commands, queue workers, scheduler output, and stderr channels.
Weaver
How can I help you explore Laravel packages today?