evolution7/silverstripe-bugsnag-logger

Bugsnag error reporting integration for Silverstripe

Silverstripe Bugsnag Logger

The Silverstripe Bugsnag Logger sends your error notifications to Bugsnag., _(*1)

Compatibility

Tested to work with both Silverstripe 2.4 and 3.x applications., _(*2)

Installation

The recommended way is using Composer., _(*3)

Add both this repository and the original bugsnag project to your project's composer.json file, _(*4)

"require": {
    "evolution7/silverstripe-bugsnag-logger": "1.*"
}

After this simply run, _(*5)

$ composer install

or, _(*6)

$ composer update evolution7/silverstripe-bugsnag-logger

As a submodule

Alternatively, if your project does not use Composer you can import the repository as a submodule., _(*7)

$ git submodule add https://github.com/evolution7/silverstripe-bugsnag-logger bugsnag-logger
$ git submodule add https://github.com/bugsnag/bugsnag-php.git vendor/bugsnag
$ git submodule update --recursive --init

Usage

After installation, all you need to do is add the following line to your _config.php to enable the Bugsnag Logger., _(*8)

E7_BugsnagLogger::enableWithApiKey(API-KEY-HERE);, _(*9)

Advanced Usage

Client configuration

Calling the enableWithApiKey method will return the Bugsnag_Client object from the official bugsnag-php library. To see what is possible with that, please see the documentation on their Github page., _(*10)

Release stages

Bugsnag allows you to determine which release stage you are currently in, the Bugsnag Logger uses a ReleaseStage class for this which determines this based on the path, but it is possible to override this by providing your own ReleaseStage class as an optional second parameter when calling enableWithApiKey. This class will have to implement the ReleaseStageInterface to ensure it has the required methods., _(*11)

E7_BugsnagLogger::enableWithApiKey(API-KEY-HERE, new CustomReleaseStage());, _(*12)

Contributing

• Fork it on Github
• Make the changes you'd like to see
• Make a pull request
• Thanks!