Weave Code
Symfony Telemetry Bundle Laravel Package
flow-php/symfony-telemetry-bundle
A Symfony bundle that integrates Flow PHP's telemetry with Symfony applications, providing tracing and instrumentation for data pipelines through OpenTelemetry. It auto-configures services, span processors, and exporters so you can observe ETL workloads with minimal setup.
At a glance
Frequently asked questions about Symfony Telemetry Bundle
- Is flow-php/symfony-telemetry-bundle compatible with Laravel?
- It is a Symfony bundle, not a Laravel package. It depends on Symfony Kernel bundle registration, a DI extension, and compiler passes, where Laravel uses service providers and illuminate/container. Composer can install it in a Laravel project, but its framework wiring will not activate Laravel request, queue, or console lifecycles. Treat it as incompatible with Laravel unless you build a custom integration around its portable core.
- Can this bundle auto-instrument Laravel queues and Artisan commands?
- No, not as shipped. Its auto-instrumentation targets Symfony hook points such as the kernel, Messenger, Console, and HttpClient. Laravel equivalents are queue events like JobProcessing, JobProcessed, and JobFailed, plus Queue::before and Queue::after and Artisan command events. You would need to rewrite the bundle's wiring against Laravel primitives rather than port it directly.
- What does flow-php/symfony-telemetry-bundle actually instrument?
- It integrates Flow PHP telemetry with Symfony applications and auto-configures services, span processors, and exporters for OpenTelemetry tracing of data pipelines. The Symfony-specific layer focuses on framework auto-configuration for ETL and telemetry workloads. The portable part is the underlying flow-php/telemetry core, not the Symfony bundle wiring itself.
- How do I install flow-php/symfony-telemetry-bundle?
- Install it with Composer using composer require flow-php/symfony-telemetry-bundle. In a Symfony app, register the bundle and configure its exporters and span processors through the bundle configuration. In Laravel, installation may succeed, but Symfony bundle registration will not run because Laravel uses service providers, so you must verify constraint resolution and wiring manually.
- Does it support Laravel 10, 11, or 12?
- There is no indicated official Laravel support. The bundle is built for Symfony's bundle system, while Laravel 10 through 12 use service providers and illuminate/container rather than Symfony HttpKernel bundle registration. Composer may resolve dependencies depending on pinned Symfony component ranges, but compatibility is not validated. Run a spike before relying on it in any Laravel version.
- Does flow-php/symfony-telemetry-bundle export traces over OTLP?
- The bundle provides OpenTelemetry tracing for Flow PHP data pipelines and auto-configures span processors and exporters. OTLP export is plausible through OpenTelemetry exporter configuration, but confirm whether it emits OTLP natively or wraps the OpenTelemetry PHP SDK. Also verify the supported exporter set and any sampling controls in the bundle configuration before adopting it.
- Is flow-php/symfony-telemetry-bundle production-ready?
- The assessment flags high risk: zero stars, zero dependents, single-vendor stewardship, and no downstream validation. Telemetry sits on every request and job hot path, so a defect can affect the entire application while community bug reports and Stack Overflow coverage are absent. API stability is unproven, and MIT licensing lets you fork but means you inherit maintenance. For production Laravel work, prefer the OpenTelemetry PHP SDK or a maintained Laravel telemetry package.
- What are alternatives to this bundle for OpenTelemetry tracing in Laravel?
- Use the OpenTelemetry PHP SDK directly or a maintained Laravel OpenTelemetry package as the substrate. Define an internal Tracer and Meter facade so vendor choice remains reversible. If Flow ETL is genuinely in scope, use flow-php/telemetry and flow-php/etl as standalone libraries behind that facade and instrument job boundaries manually. Treat this Symfony bundle as a reference implementation rather than a Laravel dependency.
- Can I use flow-php/telemetry and flow-php/etl in Laravel without the Symfony bundle?
- Yes, if you are actually adopting Flow ETL. The assessment says Flow's config builder is not framework-bound, so the core telemetry and ETL libraries are portable. Pull flow-php/etl and flow-php/telemetry as libraries, wire configuration through a thin Laravel service provider, and instrument ETL job boundaries manually. Skip the Symfony bundle layer entirely in Laravel.
- What should I check before adopting flow-php/symfony-telemetry-bundle in a Laravel app?
- Resolve whether instrumentation is event-subscriber-based and portable or kernel and DI-coupled and not portable. Confirm exporter behavior, sampling controls, PII redaction, attribute cardinality, per-span overhead, and synchronous versus batch export. Check PHP and symfony star constraints against Laravel's pinned Symfony component versions, plus commit cadence and any deprecation policy. If Flow ETL is not in scope, do not adopt this bundle for Laravel.
Weaver
How can I help you explore Laravel packages today?