With Profiling, Sentry allows you to collect and analyze performance profiles from real users in production to give you a complete picture of how your application performs in a variety of environments.

Under the hood, we're using Wikipedia's sampling profiler Excimer. The Excimer PHP extension supports PHP 7.2 and up.

Here's how to install Excimer with a Linux package manager, PECL, or build from a source.

apt-get install php-excimer

See for additional distributions.

pecl install excimer

See for more information.

git clone

cd excimer/
phpize && ./configure && make && sudo make install

Depending on your environment, you may need to enable the Excimer extension afterwards.

phpenmod -s fpm excimer
# or
phpenmod -s apache2 excimer

Sentry's performance monitoring product has to be enabled in order for Profiling to work. Check out the performance setup documentation for more detailed information.

'traces_sample_rate' => 1.0,

'traces_sample_rate' => 1.0,
// Set a sampling rate for profiling - this is relative to traces_sample_rate
'profiles_sample_rate' => 1.0,

Response time is somewhat impacted when you use the performance capabilities in your Laravel application, (depending on the traces_sample_rate you've configured). If your web server is using FastCGI, our SDK utilizes a terminable middleware, which means that the response is sent to the user before the profiling data is sent to Sentry.

If your web server isn't using FastCGI, you can run Relay locally on the same machine or a local network that can act as a proxy/agent. Doing this will make the PHP process send requests to your local Relay, which will then forward them to Sentry, instead of sending requests to Sentry directly.

To begin using Relay, check out our docs for getting started. We recommend using Relay in managed mode (which is the default).

Follow the instructions in the Relay docs to send a test event through Relay to Sentry. Don't forget to update your DSN to point to your running Relay instance. After you've set up Relay, you should see a dramatic improvement in how much your server is impacted.

Help improve this content
Our documentation is open source and available on GitHub. Your contributions are welcome, whether fixing a typo (drat!) or suggesting an update ("yeah, this would be better").