Weave Code
Treblle Laravel Laravel Package
treblle/treblle-laravel
Treblle for Laravel is a drop-in SDK that adds real-time API observability: request and response logging, performance and error monitoring, auto-generated documentation, and actionable insights with minimal setup.
The official Treblle SDK for Laravel. Seamlessly integrate Treblle to manage communication with your dashboard, send errors, and secure sensitive data.
Frequently asked questions about Treblle Laravel
- What is Treblle for Laravel used for?
- Treblle for Laravel is the official Treblle SDK for Laravel. It runs as middleware in the HTTP kernel and captures request and response payloads, masks configured fields, and sends telemetry to Treblle's SaaS API for logging, performance and error monitoring, documentation, and insights. It does not own routing, persistence, or business logic, so it stays low-coupling.
- How do I install and configure treblle/treblle-laravel in a Laravel app?
- Install it with composer require treblle/treblle-laravel, publish the package config, register the middleware, and provide your Treblle credentials through environment variables. For new installs, specify v6.1.8 because it removes the common Guzzle 8 installation conflict. Confirm the exact config keys and middleware alias in the package README for your version.
- Which Laravel and PHP versions does treblle/treblle-laravel support?
- The package targets conventional Laravel applications in the Laravel 9 through 12 range on PHP 8.1 or newer according to the supplied assessment. Always confirm the exact PHP and laravel/framework constraints in the package composer.json before upgrading. If you move to Guzzle 8, check its minimum PHP version because it may raise your runtime floor.
- What changed in treblle/treblle-laravel v6.1.8?
- v6.1.8 is a single-line dependency-widening release that permits Guzzle 8 alongside the existing Guzzle constraint. No code, config, or API surface changes are called out. In practice it removes a composer conflict for applications already on or moving toward Guzzle 8, but it is not a feature release.
- Does treblle/treblle-laravel work with Guzzle 8?
- Yes, v6.1.8 allows Guzzle 8, but resolution requires alignment across treblle/treblle-laravel, treblle/treblle-php, and laravel/framework. Run composer why guzzlehttp/guzzle after updating to see which constraint is actually in force. Also verify that the package CI tests against Guzzle 8, since being allowed and being tested are different claims.
- Will Treblle add latency or break requests if the Treblle API is unavailable?
- The middleware observes the response after your other middleware has run and sends telemetry out of band, typically at request termination or through a queued job. Queued dispatch is the safer choice when you want Treblle availability to have minimal influence on request latency. Before production, verify in staging that an unreachable or erroring Treblle endpoint fails open and does not surface as a 5xx.
- How do I mask sensitive request and response fields?
- Publish the package config and list the request and response fields you want masked; the middleware masks configured fields before shipping telemetry. Review the masked payloads in the Treblle dashboard to confirm sensitive values are removed. Treat this as part of your data-egress review, especially for partner-facing APIs.
- Where in the middleware stack should I register Treblle?
- Register it in the HTTP kernel middleware stack, because the package observes the response after your other middleware has run. Placement matters: put it where it can see the final response you care about without interfering with auth, throttling, or exception handling. It does not own routing or persistence, so it can be added or removed relative to core application concerns.
- Is Treblle suitable for high-traffic production APIs?
- It is a good fit for partner-facing APIs, debugging-heavy integrations, and pre-production environments where payload inspection has clear value. For high-volume internal RPC, the telemetry overhead and data-egress review may outweigh the insight. Use queued dispatch where possible and validate latency and failure behavior under load before enabling it broadly.
- Can I remove Treblle later without changing my application code?
- Yes. Treblle is implemented as a service provider plus middleware and does not own routing, persistence, or business logic, so removal is low-risk. You can remove the middleware and package dependency without changing core application code. Confirm any queued jobs or published config are cleaned up as part of removal.
Weaver
How can I help you explore Laravel packages today?