Laravel-native middleware
Instrument HTTP requests in the framework your team already uses, with a focused package and familiar configuration.
Laravel API monitoring
Know which customers your Laravel API issue actually affects.
Add customer context to Laravel API errors, route latency and release regressions with framework-native instrumentation and no payload capture.
Laravel-native packageTenant-aware signalsNormalized routesNo payload capture
Customer-aware observability
Customer-aware observability for Laravel APIs.
Use Laravel request context to move from a generic exception or error-rate spike to the routes, releases and customer integrations that need action.
Tenant-aware failures
Connect exceptions and failed API responses to the authenticated customer and consuming integration.
Route-level performance
Compare latency and reliability by normalized Laravel route without leaking identifiers from raw URLs.
Queue-safe delivery
Keep telemetry away from the customer response path so monitoring does not change API behavior.
Release comparisons
Find Laravel routes and customer accounts that regress after a deployment.
Privacy-safe by design
Monitor operational behavior without collecting request bodies, response bodies, cookies or credentials.
Setup
From requests to customer impact.
Keep your current logging and tracing stack. Add the customer context that generic infrastructure monitoring cannot provide.
- 1
Install the Laravel package
Add the official integration with Composer and publish its configuration.
- 2
Configure the ingestion key
Set the project key through your environment and add customer resolution for authenticated requests.
- 3
Send a test request
Call an instrumented route and confirm customer-aware traffic in your Apirelio project.
Questions
Frequently asked questions.
How do I monitor a Laravel API by customer?+
Install the Apirelio Laravel package, configure your project ingestion key and resolve the authenticated tenant or customer in the integration. Requests then appear with customer, route, status and latency context.
Will Laravel monitoring slow down API responses?+
The integration is designed to deliver telemetry away from the customer response path and to fail safely, so monitoring does not change the response returned by your application.
Does Apirelio record Laravel request bodies?+
No. Request and response bodies, credentials, cookies and query strings are excluded. Apirelio uses bounded operational metadata and the customer identifiers you explicitly provide.
Can I use it in a multi-tenant Laravel application?+
Yes. The customer resolver can use the tenant or account identity established by your authentication and tenancy layer.
Start with the requests you already serve
Know who is affected before the support ticket arrives.
Connect API reliability to customer impact with a privacy-safe event model and framework-native setup.