- Can I install m6web/log-bridge-bundle in a Laravel application?
- No. Despite frequent confusion in search results, this is a Symfony Bundle, not a Laravel package: it depends on Symfony's bundle registration lifecycle, a DependencyInjection Extension, and config/packages YAML conventions that Laravel does not have. Composer may resolve it, but nothing will wire it into Laravel's container or logging stack. Laravel teams should treat it as a reference implementation and port the pattern instead.
- How do I install and configure M6Web LogBridgeBundle in Symfony?
- Require it with composer require m6web/log-bridge-bundle, then enable the bundle in config/bundles.php and declare your bridge channels, levels, and target settings under config/packages. Because it is built on Monolog handlers and PSR-3, your existing channels keep working while the bundle forwards records to the external backend. Check the repository README for the exact configuration keys, since the option tree is bundle-specific.
- How do I use LogBridgeBundle's request and response logging in Laravel?
- Plan for a port, not an install. Reimplement it as roughly one middleware plus one Monolog processor: the middleware records method, path, status, duration, and a correlation ID (ideally in terminate so it does not sit on the response path), and the processor injects that correlation ID into every log record. Laravel's Request and Response extend Symfony HttpFoundation, so the data model transfers cleanly even though the container wiring does not. Skip the bundle's DI extension and configuration tree; a service provider and a config file cover the same ground with less code.
- Does LogBridgeBundle redact sensitive headers, cookies, and request bodies by default?
- This is the single highest-stakes unknown and must be verified by reading the handler and processor source before any pilot. Request and response logging is a PII and secrets hazard by default, because authorization headers, cookies, form bodies, and API payloads are exactly the fields you must not ship to a log aggregator. Regardless of what the bundle does, wrap capture in an explicit allowlist of headers and body fields, and add a denylist as a second line of defense.
- Which Symfony, PHP, and Monolog versions does the bundle support?
- Symfony 5.4 and 6.x are the plausible target range, but confirm it from the composer.json constraints rather than assuming. Check that symfony/http-foundation, symfony/http-kernel, and monolog/monolog resolve against your pinned components, and confirm the PHP floor. If you are aligning with a Laravel app, also confirm the Monolog major version matches the handlers configured in config/logging.php.
- Is m6web/log-bridge-bundle actively maintained and safe for production?
- Governance signals are weak: the repository has roughly 18 stars and zero dependents, so there is no ecosystem battle-testing to lean on. The Composer vendor name (m6web) diverges from the repository organization (BedrockStreaming), which is a mild rebrand-drift maintenance smell. Also verify the last release date on Packagist directly, because the recorded 2026-07-28 date looks like a metadata anomaly or forward-dated tag rather than a real publish.
- Is log capture synchronous on the request path or deferred until after the response?
- The documentation does not state this clearly, so confirm it by reading the handler source or asking the maintainer. Synchronous capture adds latency to every request and can turn a slow logging backend into an outage; deferred capture via kernel.terminate keeps the request path clean. For latency-sensitive applications, prefer a terminate-based implementation whether you adopt the bundle or port it.
- What is the difference between LogBridgeBundle and Sentry, Monolog handlers, or Symfony's MonologBundle?
- LogBridgeBundle is a thin bridge, not an APM or error-tracking platform: it forwards Monolog records from your existing channels to an external logging backend with minimal configuration. Symfony's MonologBundle already gives you handlers and channels, so the bundle's value is mostly convenience wiring for a specific backend. If you need exception grouping, tracing, or alerting, use a dedicated tool such as Sentry rather than a log bridge.
- How should I test a LogBridgeBundle integration without polluting production logs?
- Point your test and dev environments at a dedicated channel and a non-production sink, and build a functional test that asserts the handler actually receives a record for a given channel and level. If you are evaluating the bundle for a Symfony service, run it in shadow mode against a throwaway log sink for a couple of weeks before trusting it. If you are porting to Laravel, put the middleware behind a feature flag so you can disable capture instantly.
- Does it handle large file uploads and downloads without flooding the log backend?
- There is no documented size cap or streaming guard, so assume none exists until you check the source. Large multipart uploads and binary downloads can produce enormous log payloads that blow up ingestion costs or truncate records mid-JSON. Add explicit payload truncation, skip binary or streamed bodies, and cap the total serialized size per record in whatever implementation you run.