Laravel Artisan command monitoring

Know how your
Artisan commands run.

Laritor is a performance monitoring and issue tracking tool for Laravel. It records your Artisan commands, how long they take, and whether they succeed or fail. Inspect the queries, logs, and API calls behind each recorded run to find the cause of a slowdown or failure.

Try for free Explore a command

Free trial: 300K events · Unlimited apps and users

Laritor Artisan command metrics with successful and failed runs over time, success rate, failed run count, and average duration

Check run outcomesSee successful and failed executions.

Find slow operationsSee where a command spends its time.

Debug with contextInspect related events and console output.

Run history and failures

See which commands
succeed or fail.

Imports, backups, and reports can fail while your website still looks fine. Laritor helps you check the recorded runs of commands executed manually or through Laravel’s scheduler, then open a run to find out what happened.

Explore command monitoring

Check the exit code

An exit code of 0 means the command reported success. A non-zero code signals a failure. Open the run to see its details and investigate.

Find the run you need

Search by command name and filter by date or duration. Find a particular import, backup, or report run and check when it started and how long it took.

Investigate the exception

If a command throws an exception, see the error message, file, line, and stack trace. Follow its related events to understand what led to the failure.

Command execution timeline

Find out what made
a command slow.

For each recorded run, Laritor puts its queries, logs, API calls, and other events in order. See the time spent starting Laravel and executing the command, then inspect the operations behind the delay.

Explore command details

Laritor command execution timeline showing logs, an outbound HTTP request, a database query, exit code, and time spent in application boot and command execution

Events recorded with a command

Queries
Exceptions
Logs
API calls
Cache
Jobs
Mail
Notifications

Find expensive database work

Inspect the queries a command ran and how long they took. Use the details to decide where to improve a query, add an index, or reduce repeated work.

Check calls to other services

See the duration and response status of external API calls. Find out whether a command is waiting on another service or receiving an error.

Follow what happened next

Inspect dispatched jobs, cache operations, mail, and notifications alongside logs. Check which steps ran before the command finished or failed.

Console output

Read the output
from a recorded run.

See what a command printed while it was running, even after it has finished. Search its output, focus on error messages, or copy it to share with a teammate.

Choose which commands send output

Enable output recording on a command with the SendOutputToLaritor trait. Laritor then captures its console messages alongside the run’s other events.

See how to record command output

Laritor command output view with timestamped console messages, information, warning and error levels, output search, and a copy output action — Search and read captured console messages.
View screenshot

Debug with Laritor MCP

Fix command exceptions
with your AI agent.

Connect your AI coding agent to Laritor’s MCP server. When a command throws an exception, your agent can retrieve its stack trace and recorded command timeline, then use that context with your code to investigate the cause and implement a fix.

Connect Laritor MCP

AI coding agent using Laritor MCP to investigate a job exception, trace its related events, and identify the failing code — Example: an agent using Laritor’s recorded events to find the cause of a job exception. The same workflow applies to command exceptions.
MCP setup guide

Choose what to record

Track problems,
or monitor every run.

You choose how much activity Laritor records. Start with exceptions, include other detected issues, or record all command runs to monitor performance over time. Each recorded run includes its related events.

Exceptions only

Record commands that contain an exception, along with their related events.

Issues only

Record runs with detected issues, including failed commands and slow queries, with the events needed to investigate.

Full observability

Record successful runs too, to monitor command volume, success rates, and run times across your app.

Compare recording modes

Concerned about sensitive information?

Control what you send to Laritor. Filter events and redact passwords, tokens, and personal information before the recorded data leaves your servers.

Explore privacy controls

Install in under 1 minute

Start improving
your Laravel commands.

Install Laritor’s Laravel package, connect your app, and choose what to record. Find command exceptions and failures, or monitor all runs to understand their performance.

Try for free Installation guide