示例#1
0
<?php

Bugsnag::setBeforeNotifyFunction(function (Bugsnag_Error $error) {
    Bugsnag::setAppVersion(version());
});
App::error(function (Exception $e) {
    Bugsnag::notifyException($e);
    if (Config::get('app.debug')) {
        Session::flash('alert', sprintf("%s (Line %d): %s", $e->getFile(), $e->getLine(), $e->getMessage()));
    } else {
        Session::flash('alert', $e->getMessage());
    }
    return View::make('index');
});
App::error(function (DestinyException $e) {
    Bugsnag::notifyException($e);
    return View::make('error', ['error' => $e->getMessage(), 'bungie' => true]);
});
App::missing(function (Exception $e) {
    return Response::view('404', [], 404);
});
App::error(function (UnknownPlayerException $e) {
    Bugsnag::notifyException($e);
    return View::make('error', ['error' => $e->getMessage()]);
});
/*
|--------------------------------------------------------------------------
| Application & Route Filters
|--------------------------------------------------------------------------
|
| Below you will find the "before" and "after" events for the application
示例#2
0
| build a basic log file setup which creates a single file for logs.
|
*/
$logFile = php_sapi_name() . '.log';
Log::useDailyFiles(storage_path() . '/logs/' . $logFile);
/*
|--------------------------------------------------------------------------
| Bugsnag
|--------------------------------------------------------------------------
*/
// Bugsnag::setReleaseStage("production");
Bugsnag::setErrorReportingLevel(E_ALL & ~E_NOTICE);
Bugsnag::setBeforeNotifyFunction(function ($error) {
    // Do any custom error handling here
    // Also add some meta data to each error
    if (Auth::check()) {
        $user = Auth::user()->toArray();
        $error->setMetaData(array("user" => $user));
    }
});
/*
|--------------------------------------------------------------------------
| Application Error Handler
|--------------------------------------------------------------------------
|
| Here you may handle any errors that occur in your application, including
| logging them or displaying custom views for specific errors. You may
| even register several error handlers to handle different types of
| exceptions. If nothing is returned, the default error view is
| shown, which includes a detailed stack trace during debug.
|
*/