# PHP Performance Monitoring & Error Tracking > Find bottlenecks and exceptions with full stack traces and Excimer-powered profiling. Supports PHP 7.2 and above, with Laravel and Symfony guides. **URL:** https://sentry.io/for/php/ --- Actionable insights to resolve PHP performance bottlenecks and errors. See the full picture of any PHP exception with a clear workflow to create an efficient PHP debugging process. **Documentation:** [https://docs.sentry.io/platforms/php/](https://docs.sentry.io/platforms/php/) ## Features ### PHP Performance Monitoring 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. ### Complete Stack Traces, With Function Arguments 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. ### Fill In the Blanks 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. ### Your Logs, Next to the Error Send structured logs from your PHP application to Sentry and query them next to the [traces](/product/tracing/) and errors they belong to. Monolog output becomes searchable context on the request that failed, instead of a file you have to SSH in to read. Learn more about [Logs in Sentry](/product/logs/). ## FAQ **What is the difference between Sentry and traditional logging?** 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](/vs/logging/) and on our [blog](https://blog.sentry.io/lets-get-ready-to-monitor/). **What languages does Sentry support?** Sentry supports every major language, framework, and library. You can browse each of them [here](/platforms/). **How much does Sentry cost?** 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](/pricing/). **How does Sentry impact the performance of my app?** 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. **Which PHP versions does Sentry support?** The Sentry PHP SDK supports PHP 7.2 and later, and installs with Composer. There are dedicated guides for [Laravel](/for/laravel/) and [Symfony](/for/symfony/) on top of the base SDK. PHP profiling is powered by the Excimer extension, which also supports PHP 7.2 and up on Linux and macOS. To capture function arguments in your stack traces, set `zend.exception_ignore_args` to `Off`. **Does Sentry offer PHP profiling?** Yes. Sentry's PHP profiling uses the Excimer extension (installed via PECL, on Linux and macOS) to collect function-level performance data from real production traffic — no custom instrumentation needed. Profiles are linked to the traces they came from, so you can go from a slow endpoint straight to the specific function burning the time. Learn more about [Profiling](/product/profiling/). **Can I send logs to Sentry?** 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](/product/logs/). **What is Seer, Sentry's AI debugging agent?** 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](/product/seer/) and [Autofix](/product/seer/autofix/). --- *Source: [sentry.io/for/php/](https://sentry.io/for/php/)*