Flight-native middleware
Capture matched Flight routes through standard before and after hooks instead of instrumenting every handler.
FlightPHP API monitoring
Connect FlightPHP API signals to customer impact.
Trace matched routes, slow requests and release regressions to the accounts and integrations behind them with Flight-native middleware.
FlightPHP 3.10+Native middlewareCustomer contextNo payload capture
Customer-aware observability
Customer-aware observability for FlightPHP APIs.
Keep Flight's lightweight routing and error handling while adding the customer dimension generic monitoring leaves out.
Customer-aware failures
Resolve the authenticated account and consuming application behind unsuccessful requests and exceptions.
Bounded buffered delivery
Move telemetry into a locked local buffer and keep ingestion failures away from customer responses.
Route-level performance
Compare latency and reliability by matched Flight route without retaining identifiers from concrete URLs.
Release impact
Connect deployment identifiers to changed errors, latency and the customer integrations affected.
No payload capture
Keep request bodies, responses, credentials, cookies, query strings and exception messages outside the event model.
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 FlightPHP package
Add the official Composer adapter and its shared PHP Core dependency.
- 2
Register middleware and identity
Attach Apirelio to a route group and resolve the authenticated B2B account.
- 3
Inspect customer impact
Send an instrumented request and review route health, errors and releases by customer.
Questions
Frequently asked questions.
How do I monitor a FlightPHP API by customer?+
Install apirelio/flightphp, attach its middleware to a Flight route group and provide a resolver for the account established by your authentication layer.
Which FlightPHP versions are supported?+
The initial adapter supports FlightPHP 3.10 or newer on PHP 8.2 or newer.
Does FlightPHP monitoring capture request bodies?+
No. Apirelio records bounded operational metadata such as matched route, status, duration and explicit customer context—not request or response payloads.
Will an ingestion failure break my FlightPHP API?+
No. Delivery errors are contained, and the optional local buffer keeps network delivery away from normal customer responses.
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.