Symfony Span Bundle Laravel Package

Product Decisions This Supports

• Observability roadmap: whether span-level distributed tracing gets instrumented at the framework layer (bundle/middleware) versus agent- or proxy-level collection — this package represents the framework-layer option.
• Build vs buy on tracing: a concrete "assemble from OSS primitives" candidate to weigh against a paid APM vendor (Datadog, New Relic, Honeycomb) or a full OpenTelemetry SDK integration.
• Ownership model: whether tracing is a platform-team deliverable (shared instrumentation) or left to individual app teams; a bundle-based approach favors the platform team.
• Hybrid estate consolidation: for shops running both Symfony and Laravel, a Symfony-native instrumentation layer can be reused via adapters, reducing duplicated tracing work.
• Caveat for this release: v1.0.1 is a patch with no documented changes. It does not shift any of the above decisions on its own — it is a maintenance signal, not a capability signal.

When to Consider This Package

Consider it when:

• The estate is Symfony-centric, or hybrid Symfony/Laravel where HttpKernel, the DI container, and EventDispatcher are already in the request path.
• You want spans emitted via bundle autoconfiguration rather than hand-wiring an SDK in every service.
• You are standardizing on an open, vendor-neutral tracing backend and want instrumentation decoupled from the backend choice.
• The team can absorb a small-maintainer dependency: version pinning, reading diffs before upgrades, and a fork-or-replace escape hatch are acceptable.

Look elsewhere when:

• The app is Laravel-only. First-party options (Telescope, Laravel's OpenTelemetry instrumentation) are lower-friction than a Symfony bundle plus an adapter layer.
• You need vendor support, SLAs, managed upgrades, or enterprise procurement — buy the APM instead.
• Release governance matters to you. v1.0.1 shipped with a bare compare link and no changelog entry; that is a maturity signal worth pricing into the decision.
• Your tracing needs are only HTTP-client or queue-level; an SDK or agent covers that with less surface area and no framework coupling.

How to Pitch It (Stakeholders)

Executives: This is a small open-source Symfony bundle for span-level tracing, now at v1.0.1. The release is a patch with no documented changes — no new capability, no expected breakage, no cost impact. Recommendation: keep it on the evaluation list, not the committed roadmap. It is cheap to trial, but thin release hygiene and a single-maintainer profile argue against making it load-bearing without a fallback. Decision requested: fund a 1–2 day spike, or defer to next planning cycle.

Engineering: Treat v1.0.1 as backward compatible by semver, but verify — the changelog is only a diff link, so read the diff or run the suite before bumping. The package targets Symfony's bundle and DI conventions; for Laravel, budget for a thin service-provider adapter or manual wiring, and include that effort in the spike estimate. Spike success criteria: spans visible end-to-end on one real request path, measured overhead, and a documented exit path (swap to the OpenTelemetry SDK) if the package stalls or a maintainer disappears.