Weave Code
Google Cloud Trace Bundle Laravel Package
softspring/google-cloud-trace-bundle
A Symfony bundle that integrates Google Cloud Trace, adding distributed tracing to your PHP applications. It captures request spans and exports timing data to Google Cloud, helping you monitor latency, diagnose bottlenecks, and follow requests across services.
A Symfony bundle that integrates Google Cloud Trace into your application, enabling distributed tracing with minimal setup. It captures request lifecycles as spans and exports them to Google Cloud for latency analysis and debugging.
- Automatic request tracing through Symfony kernel events
- Configurable sampling rates to control overhead
- Custom span attributes and annotations for richer context
- Seamless Google Cloud credentials integration
- Console command tracing support
Frequently asked questions about Google Cloud Trace Bundle
- Is softspring/google-cloud-trace-bundle compatible with Laravel?
- No — it is a Symfony bundle, not a Laravel package. It relies on Symfony Bundle classes, DI compiler passes, and services.yaml, which Laravel does not provide. You cannot install it into a Laravel app and expect auto-wiring or HttpKernel span decoration. For Laravel, use a wrapper or OpenTelemetry instead.
- How do I add Google Cloud Trace to a Laravel application?
- Do not install this Symfony bundle directly. Build a thin Laravel integration: bind Google\Cloud\Trace\Tracer in a ServiceProvider and add a global middleware that opens a root span and closes it in terminate(). You must reproduce the X-Cloud-Trace-Context header parsing, sampling, and export logic yourself or via a library. Alternatively, adopt OpenTelemetry PHP with the GCP exporter, which is framework-agnostic.
- Can I use this bundle in Laravel with a shim or adapter?
- You can, but it creates a permanent translation layer maintained by your team, not upstream. The bundle's Symfony-specific wiring would need to be bypassed or emulated, and upstream will never test your Laravel integration. The effort is high and partly wasted compared with a direct wrapper or OpenTelemetry. Treat the package as a reference implementation to read rather than a dependency to install.
- What does softspring/google-cloud-trace-bundle actually do?
- It integrates Google Cloud Trace into Symfony applications, sending request traces and spans to Google Cloud Platform for distributed tracing and latency monitoring. It auto-wires Google\Cloud\Trace\Tracer into the container and decorates Symfony's HttpKernel to open and close root spans per request. The real engineering is in trace propagation: parsing X-Cloud-Trace-Context, making sampling decisions, and exporting spans to the Cloud Trace API.
- Does this package support OpenTelemetry?
- The evaluation provided does not state OpenTelemetry support; it describes native Cloud Trace export via the Google Cloud Trace client. A key open question for maintainers is whether the project's recommended path is now OpenTelemetry or still native Cloud Trace export. For Laravel, OpenTelemetry PHP plus the GCP exporter is the framework-agnostic option the ecosystem is moving toward. Check the diff and maintainer guidance before assuming an OTel path.
- What are the alternatives to this bundle for Laravel developers?
- Three realistic options: write a thin Laravel wrapper around google/cloud-trace directly; adopt OpenTelemetry PHP with the GCP exporter; or read this bundle as a reference implementation rather than install it. The wrapper approach requires a ServiceProvider and global middleware with terminate() for span lifecycle. OpenTelemetry is framework-agnostic and aligns with where the ecosystem is heading.
- Is it safe to use in production if trace export fails?
- Tracing is non-functional-path infrastructure, so export failures must never fail a request. Any integration should wrap export in try/catch and degrade to a no-op; a bundle that assumes a healthy collector is a latent availability risk. The evaluation flags this as a medium technical risk. Test failure modes explicitly before production rollout.
- What changed in v5.6.0 and is it a breaking change?
- The v5.6.0 changelog is only a GitHub compare link (v5.5.10...v5.6.0) with no enumerated features, deprecation notice, migration guide, or breaking-change callout. Semver convention suggests a minor bump on 5.x is backward-compatible and additive, but that inference is unverified and should not be treated as risk sign-off. You must read the diff to check for config tree changes, service ID renames, new required env vars, or minimum PHP/Symfony bumps.
- Which Symfony and PHP versions does this bundle support?
- The provided context does not list exact version constraints; that is one of the key unknowns blocking a clean estimate. You need to confirm the minimum Symfony version (whether it tracks Symfony 5.4, 6.x, or 7.x) and any minimum PHP bump in the 5.5.10 to 5.6.0 diff. Check composer.json and the release diff before committing. The project's stated 5.x support window is also unconfirmed.
- Is this package actively maintained and used in production?
- The evaluation notes an opaque release process — a changelog that is only a diff link is acceptable for a patch but questionable for a feature bump. It flags this as a signal about release discipline and maintenance risk. There is no evidence provided of production use beyond the author's own projects. Ask maintainers who consumes the bundle today before relying on it.
Weaver
How can I help you explore Laravel packages today?