Symfony Application Monitoring & Error Tracking

Actionable insights to resolve Symfony performance bottlenecks and errors. Improve your monitoring workflow with a full view of releases so you can mark Symfony errors as resolved and prioritize live issues.

Getting Started is Simple

Install the sentry/sentry-symfony bundle with Composer:

Bash
composer require sentry/sentry-symfony

Add your DSN to .env:

Env
###> sentry/sentry-symfony ###
SENTRY_DSN="<paste-your-DSN-here>"
###< sentry/sentry-symfony ###

Check our documentation for the latest instructions.

See All Platforms

More than 150K Organizations Trust Sentry with Their Application Monitoring

Symfony Performance Monitoring

Quickly identify performance issues and view full end-to-end distributed trace to see the exact, poor-performing API call and surface any related errors.

Symfony Error Monitoring with Complete Stack Traces

See local variables in the stack for prod errors, just like in your dev environment. Explore the full source code context with frame to function data. Filter and group Symfony exceptions intuitively to eliminate noise.

Fill In the Blanks About Symfony Errors

Expose the important events that led to each Symfony exception: network requests, SQL queries, debug logs, post errors. Learn in which version a bug first appeared, merge duplicates, and know if things regress in a future release.
laravel forge

Set up Sentry through Forge

If you're using Laravel's Forge platform to provision and deploy your PHP application, creating your Sentry account is as simple as a few clicks. As a preferred debugging platform for Symfony, you can set up your Sentry organization through Forge.

"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."

Sachin Fernandes
Systems Engineer at Cloudflare
Cloudflare

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 Symfony 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.

Traditional logging provides you with a trail of events. Some of those events are errors, but many times they're simply informational. Sentry is fundamentally different because we focus on exceptions, or in other words, we capture application crashes. We discuss in more detail here and on our blog.

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.

Learn more about Seer and Autofix.

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.

Supporting Resources

How Slow Is Slow

How Cloudflare Uses Sentry

Resolve Symfony errors with max efficiency, not max effort