Recorded sends
See how many mail sends Laritor recorded in the selected period. Compare activity around a release or a scheduled batch.
Laravel mail monitoring
See the emails your app sends.
Understand what triggered them.
Laritor is a performance monitoring and issue tracking tool for Laravel. Monitor email sends, search mail history, and inspect subjects and recipients. Open the request or job behind a message to investigate missing emails, repeated sends, or problems in your sending workflow.
Free trial: 300K events · Unlimited apps and users
01
Monitor mail activitySend counts and trends by mailable type.
02
Inspect individual sendsSubjects, recipients, and timestamps.
03
Follow the sending workflowOpen the request, job, command, or task.
Mailable types
See which kinds of mail contributed to the total. A mailable is the Laravel class used to build an email, such as OrderShipped.
Peak interval
Find the time bucket with the most recorded sends. Check whether that burst came from expected work or repeated executions.
Search your Laravel mail history
Find the email
you expected your app to send.
Search by subject, recipient, or mailable class. Select the period you want to inspect and look through recorded sends with their timestamps and originating executions.
Use it to check an order confirmation, find a password reset email, or investigate repeated reminders. When an expected send is missing, check the workflow and your recording settings before drawing a conclusion.
Explore mail filters
Subject, recipients, and sending metadata
Check what was sent
and who it was addressed to.
Expand a mail entry to inspect the subject, To addresses, mailable class, and recorded send time. Check whether your code chose the intended recipient and the right kind of message.
Copy the subject, recipients, or class name when you need to investigate the send with a teammate.
Subject and mailable
Check the subject your app sent and the mailable class that built it.
Recipient information
Inspect the recorded To addresses to check whether your code selected the intended recipients.
Time and origin
See when the send was recorded and open the execution that produced it.
Mail volume and mailable types
Understand which emails
make up your send volume.
A mailable is the Laravel class used to build an email. Compare types such as order confirmations, receipts, and shipping notifications to see what your app is sending.
Use the breakdown with the activity chart to investigate unexpected volume. Open the mail history to check which executions produced those sends.
Some entries appear as an anonymous mailable when no named class is recorded.
Counts reflect recorded events in the selected period. Recording modes and filters affect the history and trends you see.
The execution behind each mail
Follow a message
back to the code that sent it.
Open a mail entry’s origin to inspect the recorded request, job, command, or scheduled task. Review its logs, queries, exceptions, and other events to understand why the email was sent.
For queued mail, inspect the job that performs the send. If a workflow repeats or fails, the related activity can help you find where to make a change.
Example: sending a shipping notification through a queue
- 01An order is updatedA request starts the workflow
- 02A job processes the workYour queue handles the mail task
- 03Your app sends the emailLaritor records the mail event
- 04You inspect its originReview the job and related events
Investigate missing or repeated emails
Check the send.
Then inspect the workflow.
When a customer reports a missing email or receives a message more than once, start with recorded mail history and follow the related activity.
Inspect failed jobs, log entries, and exceptions to understand whether the workflow completed as intended.
- 01
Find the expected email
Search by subject, recipient, or mailable class and choose the relevant time window. Check the recorded send time and recipient details.
- 02
Inspect the sending workflow
Open the origin to review the request or job. If no send appears, check the expected job or task for failures, logs, or exceptions, and review your recording settings.
- 03
Verify the outcome
Correct the code, queue setup, or mail configuration as needed and test the workflow again. Use your mail provider’s records to investigate delivery, bounces, or spam filtering.
Use Laritor how you want
Track the mail activity
you care about.
Keep mail context around exceptions, keep activity with detected issues, or record successful executions too.
A missing record in a filtered mode does not by itself prove an email was not sent. Full observability gives you a broader picture of routine mail activity.
Exceptions only
Keep mail events and related activity when a request, job, command, or task contains an exception. Inspect the sends recorded during that execution.
Useful for investigating mail context around exceptions.
Issues only
Record occurrences with detected issues, such as a failed job or slow request. Inspect any related mail events alongside logs and other activity.
Focus on sending workflows with application problems.
Full observability
Record successful activity too. Follow routine sends and compare mail volume and mailable types across recorded executions.
Use this for a broader history of application mail sends.
Paid plans start at $20/month with 20M events included. Usage includes recorded mail and the other events you send. Filter unnecessary activity to reduce event usage. Estimate your usage
Recording and privacy controls
Concerned about
private data in your mail records?
Recipient addresses and subject lines can contain personal or sensitive information. Laritor applies redaction before recorded data leaves your app, and you can customize the rules for your application.
Keep the sending context your team needs while removing private information you do not need to investigate a problem.
Explore privacy controlsChoose which mail events to record.
Use recordMail($mailable, $to, $subject) to filter mail events you do not want to send.
Protect recipient information.
Customize redactEmailAddress to mask or replace email addresses. Review the outgoing data to check the result.
Handle sensitive subjects and fields.
Use redactString and redactArrayValue to customize how sensitive strings and structured values are handled.
Laravel mail monitoring questions
Understand your mail history
and what it tells you.
Answers about recorded sends, recipients, queued mail, delivery, and privacy.
What is Laravel mail monitoring?
Laravel mail monitoring helps you understand the emails your application sends and the code that triggers them. Laritor shows recorded send counts, mail activity over time, subjects, mailable classes, recipients, timestamps, and links to the requests, jobs, commands, or scheduled tasks behind each send.
Can Laritor track transactional emails sent by my Laravel app?
Yes. Use the mail history to inspect recorded sends such as order confirmations, receipts, welcome emails, password resets, and reminders. Search by subject, recipient, or mailable class and choose a date range. The available history depends on your recording mode and filters.
Can I see who an email was sent to?
Yes. Laritor’s mail history shows recorded recipient addresses. Expand an entry to inspect its subject, To addresses, mailable class, and send time. Recipient information is subject to your recording and redaction settings.
What is a Laravel mailable?
A mailable is a Laravel class used to build an email, such as an order confirmation or shipping notification. Laritor identifies recorded sends by mailable type so you can see which kinds of mail your app is sending. Some entries appear as an anonymous mailable when no named class is recorded.
Can I trace a sent email back to a request or queued job?
Yes. When a mail event belongs to a recorded execution, its origin links to the request, queued job, Artisan command, or scheduled task that sent it. Open that execution to inspect related logs, queries, exceptions, and other recorded events. For queued mail, inspect the sending job as well as the workflow that dispatched it.
How can I investigate missing or repeated emails?
Search the mail history for the expected subject, recipient, or mailable and inspect the relevant period. For repeated sends, compare timestamps and originating executions. For missing sends, check the expected request, job, or task for failures and review the recording settings. Use your mail provider’s records to investigate delivery beyond the application send.
Does a recorded send confirm inbox delivery or an email open?
No. A recorded mail send shows activity in your Laravel application. It does not confirm that the message reached the recipient’s inbox, avoided spam filtering, or was opened. Use your mail provider’s delivery records for delivery status and bounces.
Do I need full observability to monitor mail?
No. Exceptions-only and issue tracker modes keep related mail events from retained occurrences. Full observability also records successful activity for a broader mail history. Send counts and trends reflect the events you send, so a missing record in a filtered mode does not by itself prove that an email was not sent.
Can I protect email addresses and sensitive subjects?
Yes. Laritor applies redaction before recorded data leaves your app. Customize the email-address, string, and array-value redactors to handle private information in recipient addresses and subjects. Use recordMail to filter mail events you do not want to send. Review your outgoing data to check that the settings meet your needs.
Can my AI agent inspect mail context when debugging an exception?
Through Laritor MCP, a connected coding agent can retrieve an exception and its recorded execution timeline, including related mail events when available. It can use that context with your repository to investigate the failure and work on a fix.
Install in under 1 minute
See your Laravel mail activity.
Understand the work behind it.
Add Laritor’s Laravel client, choose a recording mode, and start inspecting the sends and related events your app records.
Free trial: 300K events · Unlimited apps and users