WordPress Sentry (wp-sentry)
A (unofficial) WordPress plugin to report PHP and JavaScript errors to Sentry.
This plugin can report PHP errors (optionally) and JavaScript errors (optionally) to Sentry and integrates with its release tracking.
It will auto detect authenticated users and add context where possible. All context/tags can be adjusted using filters mentioned below.
This plugin requires PHP 7.2
+ but urges users to use a PHP version that is not end of life (EOL) and no longer supported. For an up-to-date list of PHP versions that are still supported see: http://php.net/supported-versions.php.
- Version
2.1.*
of this plugin will be the last to support PHP5.3
. - Version
2.2.*
of this plugin will be the last to support PHP5.4
. - Version
3.11.*
of this plugin will be the last to support PHP7.1
.
Please note that version 4.x
is the most recent version of the wp-sentry plugin and only supports PHP 7.2
and up. If you need PHP 5.4-7.1
support check out version 2.x
or 3.x
but do keep in mind there are a lot of differences in the Sentry PHP SDK used.
- Version
2.x
of the wp-sentry plugin uses the1.x
version of the official Sentry PHP SDK. - Version
3.x
of the wp-sentry plugin uses the2.x
version of the official Sentry PHP SDK. - Version
4.x
of the wp-sentry plugin uses the3.x
version of the official Sentry PHP SDK.
- Install this plugin by cloning or copying this repository to your
wp-contents/plugins
folder - Configure your DSN as explained below
- Activate the plugin through the WordPress admin interface
Note: this plugin does not do anything by default and has no admin interface. A DSN must be configured first.
(Optionally) track PHP errors by adding this snippet to your wp-config.php
and replace PHP_DSN
with your actual DSN that you find inside Sentry in the project settings under "Client Keys (DSN)":
define( 'WP_SENTRY_PHP_DSN', 'PHP_DSN' );
Note: Do not set this constant to disable the PHP tracker.
Note: This constant was previously called WP_SENTRY_DSN
and is still supported.
(Optionally) set the error types the PHP tracker will track:
define( 'WP_SENTRY_ERROR_TYPES', E_ALL & ~E_DEPRECATED & ~E_NOTICE & ~E_USER_DEPRECATED );
(Optionally) If this flag is enabled, certain personally identifiable information is added by active integrations. Without this flag they are never added to the event, to begin with.
If possible, it’s recommended to turn on this feature and use the server side PII stripping to remove the values instead.
When enabled the current logged in user and IP address will be added to the event.
define( 'WP_SENTRY_SEND_DEFAULT_PII', true );
(Optionally) track JavaScript errors by adding this snippet to your wp-config.php
and replace JS_DSN
with your actual DSN that you find inside Sentry in the project settings under "Client Keys (DSN)":
define( 'WP_SENTRY_BROWSER_DSN', 'JS_DSN' );
Note: Do not set this constant to disable the JavaScript tracker.
Note: This constant was previously called WP_SENTRY_PUBLIC_DSN
and is still supported.
(Optionally) enable JavaScript performance tracing by adding this snippet to your wp-config.php
and replace 0.3
with your desired sampling rate (0.3
means sample ~30% of your traffic):
define( 'WP_SENTRY_BROWSER_TRACES_SAMPLE_RATE', 0.3 );
Note: Do not set this constant or set it to 0.0
to disable the JavaScript performance tracing.
(Optionally) define a version of your site; by default the theme version will be used. This is used for tracking at which version of your site the error occurred. When combined with release tracking this is a very powerful feature.
define( 'WP_SENTRY_VERSION', 'v4.6.0' );
(Optionally) define an environment of your site. Defaults to unspecified
.
define( 'WP_SENTRY_ENV', 'production' );
This plugin provides the following filters to plugin/theme developers.
Please note that some filters are fired when the Sentry trackers are initialized so they won't fire if you define them in your theme or in a plugin that loads after WP Sentry does.
You can use this filter to extend the Sentry user context for both PHP and JS trackers.
WARNING: These values are exposed to the public in the JS tracker, so make sure you do not expose anything private!
Example usage:
add_filter( 'wp_sentry_user_context', function ( array $user ) {
return array_merge( $user, array(
'a-custom-user-meta-key' => 'custom value',
));
} );
Note: This filter fires on the WordPress set_current_user
action and only if the WP_SENTRY_SEND_DEFAULT_PII
constant is set to true
.
You can use this filter to override the Sentry DSN used for the PHP tracker.
WARNING: This is not recommended, please set the DSN using the
WP_SENTRY_PHP_DSN
constant in yourwp-config.php
!
Example usage:
add_filter( 'wp_sentry_dsn', function ( $dsn ) {
return 'https://<key>:<secret>@sentry.io/<project>';
} );
Note: This filter fires on the WordPress after_setup_theme
action. It is discouraged to use this and instead define the DSN in the wp-config.php
using the WP_SENTRY_PHP_DSN
constant
You can use this filter to customize the Sentry scope.
Example usage:
add_filter( 'wp_sentry_scope', function ( \Sentry\State\Scope $scope ) {
$scope->setTag('my-custom-tag', 'tag-value');
return $scope;
} );
Note: This filter fires on the WordPress after_setup_theme
action.
You can use this filter to customize the Sentry options.
Example usage:
add_filter( 'wp_sentry_options', function ( \Sentry\Options $options ) {
// Only sample 90% of the events
$options->setSampleRate(0.9);
return $options;
} );
Note: This filter fires on the WordPress after_setup_theme
action.
You can use this filter to override the Sentry DSN used for the JS tracker.
WARNING: This is not recommended, please set the DSN using the
WP_SENTRY_BROWSER_DSN
constant in yourwp-config.php
!
Example usage:
add_filter( 'wp_sentry_public_dsn', function ( $dsn ) {
return 'https://<key>@sentry.io/<project>';
} );
You can use this filter to customize/override the Sentry options used to initialize the JS tracker.
WARNING: These values are exposed to the public, so make sure you do not expose anything private !
Example usage:
add_filter( 'wp_sentry_public_options', function ( array $options ) {
return array_merge( $options, array(
'sampleRate' => '0.5',
'blacklistUrls' => array(
'https://github.com/',
'regex:\\w+\\.example\\.com',
),
));
} );
Note: Items prefixed with regex:
in blacklistUrls and whitelistUrls option arrays will be translated into pure RegExp.
You can use this filter to customize/override the Sentry context, you can modify the user
, tags
and extra
context.
WARNING: These values are exposed to the public, so make sure you do not expose anything private !
Example usage:
add_filter( 'wp_sentry_public_context', function ( array $context ) {
$context['tags']['my-custom-tag'] = 'tag-value';
return $context;
} );
Many plugin in the WordPress ecosystem generate notices that are captured by the Sentry plugin.
This can cause a high volume of events and even slower page loads because of those events being transmitted to Sentry.
The prevent this you can set the following in your wp-config.php
to filter out errors of the notice type.
define( 'WP_SENTRY_ERROR_TYPES', E_ALL & ~E_NOTICE );
The best thing to do with an exception is to capture it yourself, however you might still want to know about it.
The Sentry plugin only captures unhandled exceptions and fatal errors, to capture handled exception you can do the following:
try {
myMethodThatCanThrowAnException();
} catch ( \Exception $e ) {
// We are using wp_sentry_safe to make sure this code runs even if the Sentry plugin is disabled
if ( function_exists( 'wp_sentry_safe' ) ) {
wp_sentry_safe( function ( \Sentry\State\HubInterface $client ) use ( $e ) {
$client->captureException( $e );
} );
}
wp_die( 'There was an error doing this thing you were doing, we have been notified!' );
}
If you need to attach extra data only for the handled exception, you could add Structured Context:
$e = new Exception('Some exception I want to capture with extra data.');
if (function_exists('wp_sentry_safe')) {
wp_sentry_safe(function (\Sentry\State\HubInterface $client) use ($e) {
$client->withScope(function (\Sentry\State\Scope $scope) use ($client, $e) {
$scope->setExtra('user_data', $e->getData());
$client->captureException($e);
});
});
}
If you need to add data to the scope in every case use configureScope
in wp_sentry_scope filter.
Since this plugin is called wp-sentry-integration
it loads a bit late which could miss errors or notices occuring in plugins that load before it.
You can remedy this by loading WordPress Sentry as a must-use plugin by creating the file wp-content/mu-plugins/wp-sentry-integration.php
(if the mu-plugins
directory does not exist you must create that too).
<?php
/**
* Plugin Name: WordPress Sentry
* Plugin URI: https://github.com/stayallive/wp-sentry
* Description: A (unofficial) WordPress plugin to report PHP and JavaScript errors to Sentry.
* Version: must-use-proxy
* Author: Alex Bouma
* Author URI: https://alex.bouma.dev
* License: MIT
*/
$wp_sentry = __DIR__ . '/../plugins/wp-sentry-integration/wp-sentry.php';
if ( ! file_exists( $wp_sentry ) ) {
return;
}
require $wp_sentry;
define( 'WP_SENTRY_MU_LOADED', true );
Now wp-sentry-integration
will load always and before all other plugins.
Note: We advise you leave the original wp-sentry-integration
in the /wp-content/plugins
folder to still have updates come in through the WordPress updater. However enabling or disabling does nothing if the above script is active (since it will always be enabled).
This is an example on how to use the before_send
callback of the Sentry SDK to only capture errors occuring in a certain theme or plugin.
See also the filter docs: wp_sentry_option.
add_filter( 'wp_sentry_options', function ( \Sentry\Options $options ) {
$options->setBeforeSendCallback( function ( \Sentry\Event $event ) {
$exceptions = $event->getExceptions();
// No exceptions in the event? Send the event to Sentry, it's most likely a log message
if ( empty( $exceptions ) ) {
return $event;
}
$stacktrace = $exceptions[0]->getStacktrace();
// No stacktrace in the first exception? Send it to Sentry just to be safe then
if ( $stacktrace === null ) {
return $event;
}
// Little helper and fallback for PHP versions without the str_contains function
$strContainsHelper = function ( $haystack, $needle ) {
if ( function_exists( 'str_contains' ) ) {
return str_contains( $haystack, $needle );
}
return $needle !== '' && mb_strpos( $haystack, $needle ) !== false;
};
foreach ( $stacktrace->getFrames() as $frame ) {
// Check the the frame happened inside our theme or plugin
// Change THEME_NAME and PLUGIN_NAME to whatever is required
// And / or modify this `if` statement to detect other variables
if ( $strContainsHelper( $frame->getFile(), 'themes/THEME_NAME' )
|| $strContainsHelper( $frame->getFile(), 'plugins/PLUGIN_NAME' )
) {
// Send the event to Sentry
return $event;
}
}
// Stacktrace contained no frames in our theme and/or plugin? We send nothing to Sentry
return null;
} );
return $options;
} );
When using the Sentry Browser integration it is possible to do some work in the client browser before Sentry is initialized to change options and/or prevent the Browser SDK from initializing at all.
You do this by defining a wp_sentry_hook
JavaScript function before the Sentry Browser JavaScript file is included (keep this function small and easy since any errors that occur in there are not tracked by the Browser SDK).
A quick example on how you would disable the Browser SDK using wp_add_inline_script
:
add_action( 'wp_enqueue_scripts', function () {
wp_add_inline_script( 'wp-sentry-browser', 'function wp_sentry_hook(options) { return someCheckInYourCode() ? true : false; }', 'before' );
} );
When the wp_sentry_hook
function returns false
the initialization of the Sentry Brower SDK will be stopped. Any other return value will be ignored.
To modify the options you can modify the object passed as the first argument of the wp_sentry_hook
, this object will later be passed to Sentry.init
to initialize the Browser SDK.
If you discover a security vulnerability within WordPress Sentry (wp-sentry), please send an e-mail to Alex Bouma at alex+security@bouma.me
. All security vulnerabilities will be swiftly addressed.
The WordPress Sentry (wp-sentry) plugin is open-sourced software licensed under the MIT license.