Sentry is an error and exception aggregation service. It takes your application's errors and stores them for later analysis and debugging.
Imagine this: You see exceptions before your client does. This means the error > report > debug > patch > deploy cycle is the most efficient it can possibly be.
This module binds Sentry.io and locally-hosted Sentry installations, to the error & exception handler of SilverStripe. If you've used systems like RayGun, Rollbar, AirBrake and BugSnag before, you'll know roughly what to expect.
- PHP5.6+, <7.2
- SilverStripe v4.0.0-rc1+
- PHP5.4+
- SilverStripe v3.1.0+ < 4.0
Add the Composer package as a dependency to your project:
composer require phptek/sentry: 1.0
Configure your application or site with the Sentry DSN into your project's YML config:
PhpTek\Sentry\Adaptor\SentryClientAdaptor:
opts:
# Example DSN only. Obviously you'll need to setup your own Sentry "Project"
dsn: http://deacdf9dfedb24ccdce1b90017b39dca:deacdf9dfedb24ccdce1b90017b39dca@sentry.mydomain.nz/44
phptek\Sentry\Adaptor\SentryClientAdaptor:
opts:
# Example DSN only. Obviously you'll need to setup your own Sentry "Project"
dsn: http://deacdf9dfedb24ccdce1b90017b39dca:deacdf9dfedb24ccdce1b90017b39dca@sentry.mydomain.nz/44
Sentry is normally setup once in your project's _config.php as follows, but see the usage docs for more detail and options.
SS_Log::add_writer(\phptek\Sentry\SentryLogWriter::factory(), SS_Log::ERR, '<=');
SS_Log::add_writer(\PhpTek\Sentry\Log\SentryLogWriter::factory(), SS_Log::ERR, '<=');
See the TODO docs for more.