- Can I use roqmeu/symfony-span-bundle in a Laravel application?
- Not in the ordinary Laravel package way. roqmeu/symfony-span-bundle is a Symfony bundle and relies on Symfony's Bundle, Extension, and compiler-pass contracts plus config/bundles.php, none of which Laravel provides. You can technically install it with Composer, but you will need to write your own Laravel service provider and middleware layer, or use the underlying Span library directly if it is framework-agnostic.
- How do I install roqmeu/symfony-span-bundle in Laravel?
- You can run composer require roqmeu/symfony-span-bundle, but it will not auto-register in Laravel and there is no bundles.php equivalent. Treat installation as only the first step: inspect composer.json, confirm whether the Span core is a normal dependency, and bind services manually in a Laravel service provider. If the bundle classes type-hint Symfony kernel or DI classes, expect to reimplement the integration layer rather than reuse it.
- Is roqmeu/symfony-span-bundle a Laravel package or a Symfony bundle?
- It is explicitly a Symfony bundle. The package description says it registers services, exposes bundle configuration, and hooks into Symfony's container so Span can be used alongside Symfony framework code. Laravel developers should evaluate it as a Symfony-oriented integration rather than a drop-in Laravel tracing package.
- Does roqmeu/symfony-span-bundle include a framework-agnostic Span library I can bind into Laravel's container?
- That is the key question to verify before committing. Check whether the bundle delegates to a separate Span library listed under Composer require, and whether that library can be used without booting a Symfony kernel. If it is genuinely framework-agnostic, you can bind it in a Laravel service provider and write your own middleware; if the bundle embeds Symfony-specific services throughout, your value shrinks to the underlying tracer plus custom integration code.
- Which Laravel versions does roqmeu/symfony-span-bundle support?
- There is no evidence that roqmeu/symfony-span-bundle tests against Laravel at all. It is a Symfony bundle, so its CI and compatibility promises are likely centered on Symfony and PHP versions. Before adopting it, check the declared php and symfony/* constraints and run a Composer solve against your target Laravel and illuminate/* pins.
- How do I add tracing middleware in Laravel if I use this bundle?
- You will need to build that layer yourself. A realistic Laravel integration includes a global middleware that opens a root span, injects trace and span IDs into the request context, propagates them into Guzzle or Http:: calls, carries context across queued jobs, and enriches log context with trace IDs. roqmeu/symfony-span-bundle does not provide Laravel middleware or those framework-specific hooks.
- What are the production risks of using roqmeu/symfony-span-bundle with Laravel?
- The main risk is framework-support drift: a Symfony bundle has no reason to test Laravel 11 or 12, and transitive symfony/* constraints can conflict with illuminate/* at upgrade time. Release hygiene is also opaque, since v1.0.1 documentation is only a compare link, and a single-maintainer namespace raises bus-factor concerns. You would own the Laravel integration layer, including middleware, queue propagation, and log enrichment.
- Does roqmeu/symfony-span-bundle v1.0.1 contain breaking changes?
- The release notes for v1.0.1 consist only of a compare link, so there is no explicit changelog or migration note. A 1.0.0 to 1.0.1 delta is almost certainly patch-level, such as a bugfix or constraint loosening, so no breaking change is implied. Still, read the diff before upgrading because blind bumps add recurring review cost.
- Are there better alternatives to roqmeu/symfony-span-bundle for Laravel tracing?
- For Laravel-first projects, evaluate OpenTelemetry PHP or Laravel-specific tracing packages that already provide middleware, HTTP client propagation, queue context, and log enrichment. If you prefer the Span ecosystem, use the underlying framework-agnostic Span library directly with your own Laravel service provider and middleware. Compare maintenance activity, Laravel version coverage, and exporter configuration before choosing.
- How should I test roqmeu/symfony-span-bundle in a Laravel app before committing?
- Prototype the integration in a branch: add the package, confirm the Composer solve on your target Laravel and PHP versions, and verify whether the Span core works without a Symfony kernel. Then build a minimal service provider and global middleware, and test trace propagation across HTTP calls, queued jobs, and log context. If those steps require reimplementing Symfony-specific services, treat the package as a tracer dependency rather than a Laravel integration.