The Bugsnag Notifier for Laravel gives you instant notification of errors and exceptions in your Laravel PHP applications. We support Laravel 5, Laravel 4, Laravel 3, and Lumen.

Bugsnag captures errors in real-time from your web, mobile and desktop applications, helping you to understand and resolve them as fast as possible. Create a free account to start capturing errors from your applications.

Check out this excellent Laracasts screencast for a quick overview of how to use Bugsnag with your Laravel apps.

• Getting Started
  • Installation
    • Laravel 5.0+
    • Laravel (Older Versions)
    • Lumen
  • Environment Variables
• Usage
  • Catching and Reporting Exceptions
  • Sending Non-fatal Exceptions
  • Configuration Options
    • Error Reporting Levels
    • Callbacks
• Demo Applications
• Support
• Contributing
• License

1. Install the bugsnag/bugsnag-laravel package

   $ composer require bugsnag/bugsnag-laravel:1.*

2. Update config/app.php to activate Bugsnag

   # Add `BugsnagLaravelServiceProvider` to the `providers` array
   'providers' => array(
       ...
       Bugsnag\BugsnagLaravel\BugsnagLaravelServiceProvider::class,
   )
   
   # Add the `BugsnagFacade` to the `aliases` array
   'aliases' => array(
       ...
       'Bugsnag' => Bugsnag\BugsnagLaravel\BugsnagFacade::class,
   )

3. Use the Bugsnag exception handler from App/Exceptions/Handler.php.

   # DELETE this line
   use Illuminate\Foundation\Exceptions\Handler as ExceptionHandler;

   # ADD this line instead
   use Bugsnag\BugsnagLaravel\BugsnagExceptionHandler as ExceptionHandler;

   After this change, your file should look like this:

   <?php namespace App\Exceptions;
   
   use Exception;
   use Bugsnag\BugsnagLaravel\BugsnagExceptionHandler as ExceptionHandler;
   
   class Handler extends ExceptionHandler {
       ...
   }

4. Create the configuration file config/bugsnag.php:

   $ php artisan vendor:publish --provider="Bugsnag\BugsnagLaravel\BugsnagLaravelServiceProvider"

5. Configure your api_key in your .env file:

   BUGSNAG_API_KEY=YOUR-API-KEY-HERE

6. Optionally, you can add the notify_release_stages key to the config/bugsnag.php file to define which Laravel environments will send Exceptions to Bugsnag.

   return array(
       'api_key' => env('BUGSNAG_API_KEY'),
       'notify_release_stages' => ['production', 'staging']
   );

For versions of Laravel before 5.0:

1. Install the bugsnag/bugsnag-laravel package

   $ composer require bugsnag/bugsnag-laravel:1.*

2. Update app/config/app.php` to activate Bugsnag

   # Add `BugsnagLaravelServiceProvider` to the `providers` array
   'providers' => array(
       ...
       'Bugsnag\BugsnagLaravel\BugsnagLaravelServiceProvider',
   )
   
   # Add the `BugsnagFacade` to the `aliases` array
   'aliases' => array(
       ...
       'Bugsnag' => 'Bugsnag\BugsnagLaravel\BugsnagFacade',
   )

3. Generate a template Bugsnag config file

   $ php artisan config:publish bugsnag/bugsnag-laravel

4. Update app/config/packages/bugsnag/bugsnag-laravel/config.php with your Bugsnag API key:

   return array(
       'api_key' => 'YOUR-API-KEY-HERE'
   );

5. Optionally, you can add the notify_release_stages key to the same file above to define which Laravel environments will send Exceptions to Bugsnag.

   return array(
       'api_key' => 'YOUR-API-KEY-HERE',
       'notify_release_stages' => ['production', 'staging']
   );

1. In bootstrap/app.php add the line

   $app->register('Bugsnag\BugsnagLaravel\BugsnagLumenServiceProvider');

   just before the line

   require __DIR__ . '/../app/Http/routes.php';

2. Change the function report in app/Exceptions/Handler.php to look like this:

   public function report(Exception $e) {
       app('bugsnag')->notifyException($e, []);
       return parent::report($e);
   }

3. Create a file config/bugsnag.php that contains your API key

   <?php # config/bugsnag.php
   
   return array(
       'api_key' => 'YOUR-API-KEY-HERE'
   );

In addition to BUGSNAG_API_KEY, other configuration keys can be automatically populated in config.php from your .env file:

• BUGSNAG_API_KEY: Your API key. You can find your API key on your Bugsnag dashboard.
• BUGSNAG_NOTIFY_RELEASE_STAGES: Set which release stages should send notifications to Bugsnag.
• BUGSNAG_ENDPOINT: Set what server to which the Bugsnag notifier should send errors. The default is https://notify.bugsnag.com, but for Bugsnag Enterprise the endpoint should be the URL of your Bugsnag instance.
• BUGSNAG_FILTERS: Set which keys are filtered from metadata is sent to Bugsnag.
• BUGSNAG_PROXY: Set the configuration options for your server if it is behind a proxy server. Additional details are available in the sample configuration.

Bugsnag works "out of the box" for reporting unhandled exceptions in Laravel and Lumen apps.

You can easily tell Bugsnag about non-fatal or caught exceptions by calling Bugsnag::notifyException:

Bugsnag::notifyException(new Exception("Something bad happened"));

You can also send custom errors to Bugsnag with Bugsnag::notifyError:

Bugsnag::notifyError("ErrorType", "Something bad happened here too");

Both of these functions can also be passed an optional $metaData parameter, which should take the following format:

$metaData =  array(
    "user" => array(
        "name" => "James",
        "email" => "james@example.com"
    )
);

Additional data can be sent with exceptions as an options hash as detailed in the [Notification Options](docs/Notification Options.md) documentation, including some [options specific to non-fatal exceptions](docs/Notification Options.md#handled-notification-options).

The Bugsnag PHP Client is available as Bugsnag, which allows you to set various configuration options. These options are listed in the documentation for Bugsnag PHP.

By default we'll use the value of error_reporting from your php.ini or any value you set at runtime using the error_reporting(...) function.

If you'd like to send different levels of errors to Bugsnag, you can call setErrorReportingLevel, for example:

Bugsnag::setErrorReportingLevel(E_ALL & ~E_NOTICE);

It is often useful to send additional meta-data about your app, such as information about the currently logged in user, along with any error or exceptions, to help debug problems.

To send custom data, you should define a before-notify function, adding an array of "tabs" of custom data to the $metaData parameter. For example:

Bugsnag::setBeforeNotifyFunction("before_bugsnag_notify");

function before_bugsnag_notify($error) {
    // Do any custom error handling here

    // Also add some meta data to each error
    $error->setMetaData(array(
        "user" => array(
            "name" => "James",
            "email" => "james@example.com"
        )
    ));
}

This example snippet adds a "user" tab to the Bugsnag error report. See the setBeforeNotifyFunction documentation on the bugsnag-php library for more information.

The Bugsnag Laravel source repository includes example applications for Laravel 4, Laravel 5, and Lumen.

Before running one of the example applications, install the prerequisites:

brew tap josegonzalez/homebrew-php
brew install php56 php56-mcrypt composer

Then open the example directory (such as example/laravel-5.1) in a terminal and start the server:

composer install
php56 artisan serve --port 8004

• Additional Documentation
• Search open and closed issues for similar problems
• Report a bug or request a feature

We'd love you to file issues and send pull requests. The contributing guidelines details the process of building and testing bugsnag-laravel, as well as the pull request process. Feel free to comment on existing issues for clarification or starting points.

The Bugsnag Laravel notifier is free software released under the MIT License. See LICENSE.txt for details.