Errors & Logging

Introduction

When you start a new Lumen project, error and exception handling is already configured for you. In addition, Lumen is integrated with the Monolog logging library, which provides support for a variety of powerful log handlers.

Configuration

Error Detail

The amount of error detail your application displays through the browser is controlled by the APP_DEBUG configuration option in your .env configuration file.

For local development, you should set the APP_DEBUG environment variable to true. In your production environment, this value should always be false.

The Exception Handler

All exceptions are handled by the App\Exceptions\Handler class. This class contains two methods: report and render. We'll examine each of these methods in detail.

The Report Method

The report method is used to log exceptions or send them to an external service like BugSnag. By default, the report method simply passes the exception to the base class where the exception is logged. However, you are free to log exceptions however you wish.

For example, if you need to report different types of exceptions in different ways, you may use the PHP instanceof comparison operator:

  1. /**
  2.  * Report or log an exception.
  3.  *
  4.  * This is a great spot to send exceptions to Sentry, Bugsnag, etc.
  5.  *
  6.  * @param  \Exception  $e
  7.  * @return void
  8.  */
  9. public function report(Exception $e)
  10. {
  11.     if ($e instanceof CustomException) {
  12.         //
  13.     }
  15.     return parent::report($e);
  16. }

Ignoring Exceptions By Type

The $dontReport property of the exception handler contains an array of exception types that will not be logged. By default, exceptions resulting from 404 errors are not written to your log files. You may add other exception types to this array as needed.

The Render Method

The render method is responsible for converting a given exception into an HTTP response that should be sent back to the browser. By default, the exception is passed to the base class which generates a response for you. However, you are free to check the exception type or return your own custom response:

  1. /**
  2.  * Render an exception into an HTTP response.
  3.  *
  4.  * @param  \Illuminate\Http\Request  $request
  5.  * @param  \Exception  $e
  6.  * @return \Illuminate\Http\Response
  7.  */
  8. public function render($request, Exception $e)
  9. {
  10.     if ($e instanceof CustomException) {
  11.         return response()->view('errors.custom', [], 500);
  12.     }
  14.     return parent::render($request, $e);
  15. }

HTTP Exceptions

Some exceptions describe HTTP error codes from the server. For example, this may be a "page not found" error (404), an "unauthorized error" (401) or even a developer generated 500 error. In order to generate such a response from anywhere in your application, use the following:

  1. abort(404);

The abort method will immediately raise an exception which will be rendered by the exception handler. Optionally, you may provide the response text:

  1. abort(403, 'Unauthorized action.');

This method may be used at any time during the request's lifecycle.

Logging

The Lumen logging facilities provide a simple layer on top of the powerful Monolog library. By default, Lumen is configured to create daily log files for your application which are stored in the storage/logs directory. You may write information to the logs using the Log facade:

  1. <?php
  3. namespace App\Http\Controllers;
  5. use Log;
  6. use App\Http\Controllers\Controller;
  8. class UserController extends Controller
  9. {
  10.     /**
  11.      * Show the profile for the given user.
  12.      *
  13.      * @param  int  $id
  14.      * @return Response
  15.      */
  16.     public function showProfile($id)
  17.     {
  18.         Log::info('Showing user profile for user: '.$id);
  20.         return view('user.profile', ['user' => User::findOrFail($id)]);
  21.     }
  22. }

The logger provides the seven logging levels defined in RFC 5424: debug, info, notice, warning, error, critical, and alert.

  1. Log::debug($error);
  2. Log::info($error);
  3. Log::notice($error);
  4. Log::warning($error);
  5. Log::error($error);
  6. Log::critical($error);
  7. Log::alert($error);

Contextual Information

An array of contextual data may also be passed to the log methods. This contextual data will be formatted and displayed with the log message:

  1. Log::info('User failed to login.', ['id' => $user->id]);