Laravel request monitoring

Find the cause of
slow and failed requests.

Laritor is a performance monitoring and issue tracking tool for Laravel. It shows how long your requests take, which ones fail, and the queries, logs, and API calls behind them, so you can find the cause and improve performance.

Try for free Explore a request

Free trial: 300K events · Unlimited apps and users

Laritor request metrics showing traffic over time, successful and failed responses, success rate, and peak P95 latency

Monitor performanceSee traffic, response times, and failures.

Understand the causeInspect the events behind each request.

Improve your appOptimize slow operations and fix errors.

Find request problems

Find slow requests,
failures, and bot traffic.

Laritor organizes slow, failed, and bot requests into views you can investigate. See which URLs are affected, when the problem happened, and how long each request took.

Current Laritor dark interface listing the slowest requests with their timestamps, URLs, and durations — Laritor lists your slowest requests with their response times. Open a request’s timeline to find slow queries, repeated work, or API calls you can optimize to make it faster.
View screenshot

Find a specific request.

Combine filters to find a slow route, an error in a specific time window, or requests from a particular user. Group by route, URL, or user to spot patterns.

See how request filters work

Route
URL
User
HTTP method
Status code
Duration
Memory
Date range

Understand request performance

See why a request
is taking too long.

For each recorded request, Laritor puts its queries, logs, API calls, and other events in a timeline. See which operations ran, how long they took, and the time spent in Laravel startup, middleware, controllers, and rendering.

Explore request details

Current Laritor request execution timeline with queries, logs, jobs, feature flags, N+1 and duplicate query labels, and a breakdown of time spent in each Laravel stage

Events recorded with a request

Queries
Exceptions
Logs
API calls
Cache
Jobs
Mail
Notifications
Feature flags
Custom events

Optimize the slow operation

Find the query, cache miss, or external API call behind a delay. Inspect its details to decide where to add an index, improve caching, or reduce work.

Reduce unnecessary queries

Laritor highlights duplicate and N+1 queries, where related records are loaded one at a time. Find where they happen and update your code to avoid repeated database calls.

Protect sensitive information

Choose which request and response data to record. Mask passwords, tokens, and personal details before they leave your servers, while keeping the context you need to debug.

See privacy controls

Users and sessions

Follow a user’s
journey through your app.

Laritor connects the recorded requests made during a user’s session. See their entry and exit pages, follow the requests in between, and open any slow or failed request to understand what they experienced.

Understand actions within the journey

Add custom events for actions such as checkout steps, signups, or payment retries. See them alongside request events to understand what led to a delay or failure.

Explore custom events

Current Laritor dark session view with recorded request count, activity span, entry and exit requests, user, and client details — A user’s session, with its recorded requests and client details.
↗

Get help investigating and fixing problems

Debug with in-app AI
or your own AI agent.

Laritor gives AI the details behind a problem, including recorded events, queries, and exception information. Get help understanding the cause and deciding what to change.

Ask Laritor’s in-app AI

Open a request and ask Laritor’s in-app AI for optimization recommendations. It uses the recorded timeline and your database schema to suggest improvements to queries, caching, middleware, and API calls.

Set up in-app AI

Give your coding agent the debugging context

Laritor’s MCP server connects your AI coding agent to your monitoring data. Your agent can retrieve an exception’s stack trace and recorded request timeline, then use that context with your code to investigate and implement a fix.

Connect Laritor MCP

Laritor in-app AI identifying response rendering as the main delay in a 1042ms request and recommending eager loading to reduce N+1 queries — Laritor identifies the slow operation and suggests changes to improve request performance.
Set up in-app AI

Choose what to record

Choose how much to monitor.

Choose to record requests with exceptions, include other problems such as failures and slow responses, or record all activity. Each recorded request includes its related events.

Exceptions only

Record a request and its related events when an exception occurs.

Issues only

Also record other problems, such as failed or slow requests, with their related events.

Full observability

Record successful requests too, so you can track response times and traffic across your app.

Compare recording modes

Install in under 1 minute

Start improving
your Laravel requests.

Install Laritor’s Laravel package, connect your app, and choose what to record. Start with exception tracking or monitor your request performance over time.

Try for free Installation guide