Monitor your Laravel routes.
Find the endpoints that need attention.

Laravel route monitoring groups recorded requests by their route so you can compare endpoint traffic, response times, memory, and HTTP errors. Laritor is a Laravel performance monitoring and issue tracking tool that helps you identify routes needing attention and open their requests to inspect the related execution events.

A route describes the endpoint pattern and HTTP method, such as GET /products/{id}. Individual requests can contain different parameter values while matching the same route. Laritor’s route views help you compare the endpoint as a group, then open individual requests for the actual URL and execution details. Different HTTP methods can appear separately.

Compare average duration and p90 or p95 in the route list, or sort by those columns. The current Slow routes filter selects routes whose recorded average duration is at least one second. A route with a lower average can still have slow individual responses, so inspect its percentiles, duration trend, and matching requests too.

A percentile describes where a duration falls within a set of recorded responses. p95 helps you see slower responses that an average can hide. Charts show values for each time interval; summaries built from stored intervals can show the highest interval percentile rather than one exact percentile across all requests. Use the same time window and inspect individual requests when investigating a change.

The HTTP error rate is the number of recorded 4xx and 5xx responses divided by recorded requests for the route in the selected period. The response breakdown separates 2xx successes, 3xx redirects, 4xx client errors, and 5xx server errors. An HTTP error response does not necessarily mean an exception was thrown.

Yes. Open the route and use View requests, or follow a response category such as 4xx or 5xx to matching requests in the selected period. Open an affected request to inspect its status, duration, queries, outbound requests, logs, exceptions, and other events recorded with that execution.

Yes. The route response breakdown includes bot and suspicious request counts with links to matching activity. These classifications can overlap with any HTTP status and with each other, so they are not extra response categories to add to the request total. Inspect URLs, IP addresses, and user agents to inform filtering or rate-limiting rules in your application or firewall.

Yes. The route timing view shows recorded average time in framework booting, middleware, controller work, and response rendering. Use it to choose which stage to inspect, then open individual request timelines for the events inside that work. The sum of phase averages can differ from the end-to-end average duration.

They reflect the requests Laritor records. Exceptions-only and issue tracker modes retain selected problematic occurrences, while full observability also records successful activity. Filters and limits affect the available data. Filtered route counts, durations, and HTTP error rates should not be treated as measurements of all application traffic.

Install and configure the Laritor Laravel client to record supported requests and their route context. You do not need a separate custom event call for every route. Choose a recording mode, review request filters and privacy settings, and open Routes in Laritor to inspect the available activity. Custom events can add application-specific milestones when useful.