CakePHP-native middleware
Capture matched CakePHP routes through the standard PSR-15 pipeline instead of instrumenting every controller.
CakePHP API monitoring
Trace matched routes, slow requests and release regressions to the accounts and integrations behind them with CakePHP-native PSR-15 middleware.
Customer-aware observability
Keep CakePHP's request pipeline and error handling while adding the customer dimension generic monitoring leaves out.
Capture matched CakePHP routes through the standard PSR-15 pipeline instead of instrumenting every controller.
Resolve the authenticated account and consuming application behind unsuccessful requests and exceptions.
Move telemetry into a locked local buffer and keep ingestion failures away from customer responses.
Compare latency and reliability by matched CakePHP route without retaining identifiers from concrete URLs.
Connect deployment identifiers to changed errors, latency and the customer integrations affected.
Keep request bodies, responses, credentials, cookies, query strings and exception messages outside the event model.
Setup
Keep your current logging and tracing stack. Add the customer context that generic infrastructure monitoring cannot provide.
Add the official Composer adapter and its shared PHP Core dependency.
Place Apirelio after routing and resolve the authenticated B2B account.
Send an instrumented request and review route health, errors and releases by customer.
Questions
Install apirelio/cakephp, add its middleware after CakePHP RoutingMiddleware and provide a resolver for the account established by your authentication layer.
The initial adapter supports CakePHP 4.5 and 5.x on PHP 8.2 or newer.
No. Apirelio records bounded operational metadata such as matched route, status, duration and explicit customer context—not request or response payloads.
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
Connect API reliability to customer impact with a privacy-safe event model and framework-native setup.