Weave Code
Flare Debug Sender Laravel Package
spatie/flare-debug-sender
A debug sender for Flare payloads, intended mainly for internal testing. It lets Laravel apps route error, trace, and Zipkin payloads through a configurable channel, with options to pass through data, alter tracing IDs and times, print payload details, and customize curl sender settings.
Debugging tool for Flare payloads
Frequently asked questions about Flare Debug Sender
- What is spatie/flare-debug-sender used for?
- It is a debug sender for Flare payloads, intended mainly for internal testing. In a Laravel app it lets you inspect what error, trace, and Zipkin payloads Flare would receive by routing them through a configurable channel such as Ray, the Laravel log, or a file. It is a developer convenience rather than platform infrastructure.
- How do I install spatie/flare-debug-sender in Laravel?
- Run composer require spatie/flare-debug-sender, then publish Flare's config with php artisan vendor:publish --tag=flare-config. In config/flare.php set the sender class to Spatie\FlareDebugSender\FlareDebugSender and add the config block from the README. No application code changes or new services are required.
- How do I configure the Flare debug sender in config/flare.php?
- Replace Flare's sender class with Spatie\FlareDebugSender\FlareDebugSender and supply the config array. Toggles include passthrough_errors, passthrough_traces, passthrough_zipkin, replace_tracing_ids, replace_tracing_times, print_full_payload, print_endpoint, and print_resource. Choose a channel such as LaravelLogDebugChannel or RayDebugChannel, and optionally customize the underlying CurlSender options.
- Which Laravel and Flare versions does this package support?
- The package is a Laravel integration around Flare's sender config hook, and release 2.0.0 follows Flare v3. Your installed Flare SDK must expose the sender configuration hook assumed by the README, so verify that against your actual Flare version before adopting. Pin the package version and bump it when you upgrade Flare majors.
- Can spatie/flare-debug-sender be used in production?
- It is intended for local debugging and internal testing, not production telemetry. If misconfigured in a shared environment it can silently stop real errors from reaching Flare, which is the highest-severity risk. Gate it to local environments or keep the config uncommitted, and never copy the sample TLS-verification-disabled curl options into shared config.
- What channels can the debug sender output to?
- It ships with pluggable channels, including RayDebugChannel if your team already uses Ray, LaravelLogDebugChannel for the Laravel log, and a plain file channel. The Laravel log or file channel adds no new tooling to the stack. Pick the channel that gives you payload visibility with the least toolchain change.
- How is this different from Laravel Telescope or Xdebug?
- Telescope and Xdebug answer different questions, such as query analysis and step-through debugging. This package answers only "what would Flare have received?" by intercepting error, trace, and Zipkin payloads before they are sent. They can be used together without overlap conflict.
- Why does the package disable TLS verification in the sample config?
- The sample config sets CURLOPT_SSL_VERIFYHOST and CURLOPT_SSL_VERIFYPEER to 0 for local throwaway use. That is fine for a local debugging setup but must never be copy-pasted into shared or production config. Remove those curl options outside local development.
- How do I test or validate Flare payloads with this package?
- Point the sender at LaravelLogDebugChannel or a file channel, enable print options as needed, and trigger representative errors in a local environment. Inspect the normalized tracing IDs and times if replace_tracing_ids or replace_tracing_times are enabled. Use payload diffing before and after Flare upgrades as a cheap validation gate.
- Is spatie/flare-debug-sender maintained and safe to adopt?
- It is MIT licensed and has a single-vendor authorship, with low external validation such as stars and dependents. Treat it as an unsupported developer convenience with a documented escape hatch rather than platform infrastructure. Pin the version, name an internal owner for error-reporting tooling, and verify the Flare sender hook before adoption.
Weaver
How can I help you explore Laravel packages today?