Profiling for PHP is supported with Sentry PHP SDK version
3.15.0 and above.
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. Use Excimer version 1.1.0 and above for PHP 8.2.
Excimer requires Linux and doesn't support Windows or macOS.
Here's how to install Excimer with a Linux package manager, PECL, or build from a source.
apt-get install php-excimer
See https://www.mediawiki.org/wiki/Excimer for additional distributions.
pecl install excimer
See https://pecl.php.net/package/excimer for more information.
git clone https://github.com/wikimedia/mediawiki-php-excimer.git 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. To begin capturing profiling data, you first need to start a transaction. Check out the performance setup and custom instrumentation documentation for more detailed information.
\Sentry\init([ 'dsn' => 'https://examplePublicKey@o0.ingest.sentry.io/0', 'traces_sample_rate' => 1.0, ]);
\Sentry\init([ 'dsn' => 'https://examplePublicKey@o0.ingest.sentry.io/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 PHP application, (depending on the
traces_sample_rate you've configured). This is due to the nature of PHP, where requests are usually sent as part of the process in which you serve your users' response. This affects the time it takes to send a request to Sentry because it's added to your servers' response time.
To offset this and make the addition close to zero, 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.