Laravel Application Monitoring & Error Tracking
Laravel application monitoring that turns actionable insight into faster fixes. Monitor your Laravel application end to end with a complete monitoring system spanning errors, performance, and releases, so you can mark Laravel errors as resolved and prioritize live issues.
Install the sentry/sentry-laravel package with Composer:
composer require sentry/sentry-laravelAdd Sentry reporting to bootstrap/app.php:
<?php
use Illuminate\Foundation\Application;
use Illuminate\Foundation\Configuration\Exceptions;
use Illuminate\Foundation\Configuration\Middleware;
use Sentry\Laravel\Integration;
return Application::configure(basePath: dirname(__DIR__))
->withRouting(
web: __DIR__.'/../routes/web.php',
commands: __DIR__.'/../routes/console.php',
health: '/up',
)
->withMiddleware(function (Middleware $middleware) {
//
})
->withExceptions(function (Exceptions $exceptions) {
Integration::handles($exceptions);
})->create();Enable Sentry Tracing in config/sentry.php:
// Specify a fixed sample rate:
'traces_sample_rate' => 0.2,
// Or provide a custom sampler:
'traces_sampler' => function (\Sentry\Tracing\SamplingContext $context): float {
// return a number between 0 and 1
},Run this Artisan command to configure the Sentry DSN:
php artisan sentry:publish --dsn=<paste-your-DSN-here>More than 150K Organizations Trust Sentry with Their Application Monitoring
Laravel Performance Monitoring
Complete Stack Traces, With Request Context
Fill In the Blanks
Set up Sentry through Forge
Your Logs, Next to the Error
Send your Laravel logs to Sentry and query them next to the traces and errors they belong to. Monolog output becomes searchable context on the request, queued job, or Artisan command that failed.
Learn more about Logs in Sentry.
"Sentry gives us a good overview of any possible issues that were caused by a release, and the ability to fix them before they become real problems."
See the Full Picture of Any Exception
Aggregate errors by factors like request details, user ID, and app version to see what's new, a priority, or a trend.
Assign custom key-value tags to reproduce the error environment specific to your application, business, and users.
Find answers to key questions: Was it a code error or usage exception? In which app release did the Laravel bug occur?
FAQs
Yes, please see our docs for more details.
Profiling for PHP is supported with Sentry Laravel SDK version 3.3.0 and above. Please see the docs for more details.
The Laravel SDK automatically instruments your application to capture transactions and adds spans for the following features:
- Views
- Queue jobs
- Caches
- Notifications
- Database queries
- Redis operations
- Laravel HTTP Client requests
- GraphQL operations (when using Lighthouse)
- Folio page based routes
- Livewire components
Please see our Laravel SDK documentation for more details.
Sentry's Laravel SDK supports PHP 7.2 and up.
Sentry supports 8.x, 9.x and 10.x as well as Laravel Lumen 8.x, 9.x and 10.x. Older versions of the SDK support Laravel from version 4.x.
Please see our Laravel SDK docs for more information.
Yes, Sentry supports Scheduled Tasks monitoring in Laravel with Sentry Crons.
Sentry supports every major frontend language, framework, and library. You can browse each of them here.
You can get started for free. Pricing depends on the number of monthly events, transactions, and attachments that you send Sentry. For more details, visit our pricing page.
Sentry doesn't impact a web site's performance.
If you look at the configuration options for when you initialize Sentry in your code, you'll see there's nothing regarding minimizing its impact on your app's performance. This is because our team of SDK engineers already developed Sentry with this in mind.
Sentry is a listener/handler for errors that asynchronously sends out the error/event to Sentry.io. This is non-blocking. The error/event only goes out if this is an error.
Global handlers have almost no impact as well, as they are native APIs provided by the browsers.
Yes. Sentry Logs lets you send, view, and query structured logs from your application alongside your errors and traces. Because logs sit next to the error and the trace that produced them, you get the granular context — retries, API failures, internal state — that spans and stack traces alone can miss, without switching tools.
Learn more about Logs in Sentry.
Seer is Sentry's AI debugging agent. It reads the full context Sentry already has — the error, its stack trace, the surrounding trace, logs, and profiles — to find the root cause of an issue and propose a fix. Seer can open a pull request with that fix, hand the work to an external coding agent, or review your PRs before they ship.
Yes. Sentry Uptime Monitoring checks your critical URLs on a schedule and alerts you when they stop responding, so you find out before your users do. Downtime is correlated with the errors and traces from the same window, so you can go straight from "the site is down" to the code that broke it.
Learn more about Uptime Monitoring and Cron Monitoring.