sentry/sdk package with Composer:
composer require sentry/sdk
To capture all errors, even the one during the startup of your application, you should initialize the Sentry PHP SDK as soon as possible.
Sentryinit(['dsn' => 'https://<key>@sentry.io/<project>' ]);
Quickly identify PHP performance issues and view full end-to-end distributed trace to see the exact, poor-performing API call and surface any related errors. Get the real-time data and detailed reporting you need to solve performance issues early.
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 PHP exceptions intuitively to eliminate noise.
Expose the important events that led to each PHP exception: warnings, past errors, custom breadcrumbs. Get a full view of releases so you can mark errors as resolved and prioritize live issues.
Aggregate errors by factors like request details, user ID, and app versions 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.
Answer the most important questions: How actionable is the error? Can I snooze the alert?
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.