clowdy/laravel-raven

Sentry (Raven) error monitoring for Laravel with send in background

Abandoned use twineis/raven-php instead

Laravel Raven Sentry (Raven) error monitoring for Laravel 4 & 5 with send in background using queues, _(*1)

, _(*2)

Sentry (Raven) error monitoring for Laravel 5 with send in background using queues. This will add a listener to Laravel's existing log system. It makes use to Laravel's queues to push messages into the background without slowing down the application., _(*3)

, _(*4)

Installation

Add the package to your composer.json and run composer update., _(*5)

{
    "require": {
        "clowdy/laravel-raven": "2.1.*"
    }
}

Add the service provider in config/app.php:, _(*6)

Clowdy\Raven\RavenServiceProvider::class,

Register the Raven alias:, _(*7)

'Raven' => Clowdy\Raven\Facades\Raven::class,

Looking for a Laravel 4 compatible version?

Checkout the 1.0 branch, _(*8)

Configuration

Publish the included configuration file:, _(*9)

$ php artisan vendor:publish

Change the Sentry DSN by using the RAVEN_DSN env variable or changing the config file:, _(*10)

RAVEN_DSN=your-raven-dsn

This library uses the queue system, make sure your config/queue.php file is configured correctly. You can also specify the connection and the queue to use in the raven config. The connection and queue must exist in config/queue.php. These can be set using the RAVEN_QUEUE_CONNECTION for connection and RAVEN_QUEUE_NAME for the queue., _(*11)

RAVEN_QUEUE_CONNECTION=redis
RAVEN_QUEUE_NAME=error

The job data can be quite large, ensure you are using a queue that can support large data sets like redis or sqs. If the job fails to add into the queue, it will be sent directly to sentry, slowing down the request, so its not lost., _(*12)

Usage

To monitor exceptions, simply use the Log facade or helper:, _(*13)

Log::error($exception);

// or

logger()->error($exception);

You can change the logs used by changing the log level in the config by modifying the env var., _(*14)

RAVEN_LEVEL=error

Event Id

There is a method to get the latest event id so it can be used on things like the error page., _(*15)

Raven::getLastEventId();

Context information

You can pass additional information as context like this:, _(*16)

Log::error('Oops, Something went wrong', [
    'user' => ['name' => $user->name, 'email' => $user->email]
]);

User data can alternatively be added to the context of any messages sent via a processor, such as the included UserDataProcessor; see below., _(*17)

Included optional processors

UserDataProcessor

This processor attaches data about the current user to the error report., _(*18)

'processors' => [
    Clowdy\Raven\Processors\UserDataProcessor::class,
],

Or, to configure the UserDataProcessor object:, _(*19)

'processors' => [
    new Clowdy\Raven\Processors\UserDataProcessor([
        'only' => ['id', 'username', 'email'], // This is ['id'] by default; pass [] or null to include all fields
        'appends' => ['normallyHiddenProperty'],
    ]),
],

See the UserDataProcessor source for full details., _(*20)

LocaleProcessor

This processor attaches to the error report the current application locale as a tag., _(*21)

'processors' => [
    Clowdy\Raven\Processors\LocaleProcessor::class,
],

Credits

This package was inspired rcrowe/Raven., _(*22)