- Is juliendidier/buzz-profiler-bundle a Laravel package?
- No. It is a Symfony2 bundle that registers a DataCollector with the Symfony Profiler and Web Debug Toolbar through the bundle system, DI extension, and data_collector service tag. Laravel does not provide those extension points, so the package cannot be installed as a Laravel dependency. For Laravel, use Telescope's HTTP client watcher or Clockwork to inspect outbound requests.
- How do I install and register BuzzProfilerBundle in a Symfony application?
- Install it with Composer, register the bundle in AppKernel for a legacy Symfony 2.x app, then install assets and clear the cache. Registration is handled through the bundle system with no manual service wiring. Treat it as a development-only tool and keep it out of production configuration.
- Which Symfony and PHP versions does BuzzProfilerBundle support?
- The bundle targets the Symfony 2 API and its DataCollector and service definitions are written against that era. Symfony 2.x has been unsupported since 2018, and the declared symfony and PHP constraints will likely fail Composer resolution on PHP 8 and Symfony 4 or later. Expect hard conflicts if you try to add it to a modern dependency graph.
- Does it work with Laravel Telescope or Laravel's HTTP client?
- No. The collector is built for the Symfony Profiler contract and the Buzz HTTP client, not for Laravel's Telescope Watcher contract. Porting it would mean replacing the bundle bootstrap with a service provider, reimplementing the collector as a Telescope watcher, and rewriting the panel view. That effort only makes sense if you are also committing to Buzz, which is itself abandoned.
- What does the Buzz panel capture for each outgoing request?
- It captures request and response details for every Buzz HTTP call, including the method, URL, headers, status code, and duration. The panel lists each request so you can inspect outbound API traffic from the toolbar and profiler. This helps diagnose slow or failing external API calls without leaving the Symfony app.
- Does BuzzProfilerBundle redact Authorization headers or sensitive request data?
- There is no evidence of redaction in the available context, so assume it does not. Symfony profilers persist captured data under var/cache/<env>/profiler, and HTTP clients routinely carry bearer tokens, API keys, and PII. Without redaction, secrets can land in plaintext on disk and appear in the profiler UI. Verify storage behavior before enabling it anywhere real credentials are used.
- Is it safe to enable the Buzz profiler in production or shared staging?
- No. This is a development debugging tool, and the profiler storage can expose full request and response payloads. Restrict profiler access, exclude it from shared or staging environments, and never leave captured credentials on disk. Gate the bundle strictly to local development.
- What are the Laravel alternatives for debugging outbound HTTP requests?
- Use Laravel Telescope's HTTP client watcher, Clockwork, or Laravel Debugbar. These are maintained and integrate natively with Laravel's service container and events. They deliver strictly more capability than porting a Symfony2 bundle would. Telescope is the closest match for inspecting method, URL, status, headers, and timing.
- Is BuzzProfilerBundle maintained, and can I depend on it long term?
- The project shows 15 stars and zero dependents, with no upstream maintainer activity, so there is no external signal that it works against real Buzz versions. Treat it as frozen and pin the current version if you must use it. Decide internally who owns the fork, because there is no community triage or upstream fixes.
- Does it support Guzzle or symfony/http-client, or only Buzz?
- It only instruments the Buzz HTTP client, so Guzzle and symfony/http-client calls will not appear in its panel. For modern Symfony, the native HttpClientDataCollector on Symfony 4.3 and later covers symfony/http-client. The practical migration target away from Buzz is symfony/http-client or Guzzle behind PSR-18 and PSR-17, which unlocks native instrumentation on both Symfony and Laravel.