Errors & Logging

    When you start a new Laravel project, error and exception handling is already configured for you. The class is where all exceptions triggered by your application are logged and then rendered back to the user. We'll dive deeper into this class throughout this documentation.

    For logging, Laravel utilizes the library, which provides support for a variety of powerful log handlers. Laravel configures several of these handlers for you, allowing you to choose between a single log file, rotating log files, or writing error information to the system log.

    The debug option in your config/app.php configuration file determines how much information about an error is actually displayed to the user. By default, this option is set to respect the value of the APP_DEBUG environment variable, which is stored in your .env file.

    For local development, you should set the APP_DEBUG environment variable to true. In your production environment, this value should always be false. If the value is set to true in production, you risk exposing sensitive configuration values to your application's end users.

    Log Storage

    Out of the box, Laravel supports writing log information to single files, daily files, the syslog, and the errorlog. To configure which storage mechanism Laravel uses, you should modify the log option in your config/app.php configuration file. For example, if you wish to use daily log files instead of a single file, you should set the log value in your app configuration file to daily:

    Maximum Daily Log Files

    When using the daily log mode, Laravel will only retain five days of log files by default. If you want to adjust the number of retained files, you may add a log_max_files configuration value to your app configuration file:

    1. 'log_max_files' => 30

    When using Monolog, log messages may have different levels of severity. By default, Laravel writes all log levels to storage. However, in your production environment, you may wish to configure the minimum severity that should be logged by adding the log_level option to your app.php configuration file.

    1. 'log_level' => env('APP_LOG_LEVEL', 'error'),

    Custom Monolog Configuration

    If you would like to have complete control over how Monolog is configured for your application, you may use the application's configureMonologUsing method. You should place a call to this method in your bootstrap/app.php file right before the $app variable is returned by the file:

    1. $app->configureMonologUsing(function ($monolog) {
    2.     $monolog->pushHandler(...);
    3. });
    5. return $app;

    Customizing The Channel Name

    By default, Monolog is instantiated with name that matches the current environment, such as production or local. To change this value, add the log_channel option to your app.php configuration file:

    1. 'log_channel' => env('APP_LOG_CHANNEL', 'my-app-name'),

    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 is used to log exceptions or send them to an external service like or Sentry. By default, the report method 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:

    The report Helper

    Sometimes you may need to report an exception but continue handling the current request. The report helper function allows you to quickly report an exception using your exception handler's report method without rendering an error page:

    2. {
    3.     try {
    4.         // Validate the value...
    5.     } catch (Exception $e) {
    6.         report($e);
    7.         return false;
    8.     }
    9. }

    Ignoring Exceptions By Type

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

    1. /**
    2.  * A list of the exception types that should not be reported.
    3.  *
    4.  * @var array
    5.  */
    6. protected $dontReport = [
    7.     \Illuminate\Auth\AuthenticationException::class,
    8.     \Illuminate\Auth\Access\AuthorizationException::class,
    9.     \Symfony\Component\HttpKernel\Exception\HttpException::class,
    10.     \Illuminate\Database\Eloquent\ModelNotFoundException::class,
    11.     \Illuminate\Validation\ValidationException::class,
    12. ];

    The Render Method

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

    Instead of type-checking exceptions in the exception handler's report and render methods, you may define report and render methods directly on your custom exception. When these methods exist, they will be called automatically by the framework:

    1. <?php
    3. namespace App\Exceptions;
    5. use Exception;
    7. class RenderException extends Exception
    8. {
    9.     /**
    10.      * Report the exception.
    11.      *
    12.      * @return void
    13.      */
    15.     {
    16.         //
    18.     /**
    19.      * Render the exception into an HTTP response.
    20.      *
    21.      * @param  \Illuminate\Http\Request
    22.      * @return \Illuminate\Http\Response
    23.      */
    24.     public function render($request)
    25.     {
    26.         return response(...);
    27.     }
    28. }

    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, you may use the abort helper:

    The abort helper 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.');

    Custom HTTP Error Pages

    Laravel makes it easy to display custom error pages for various HTTP status codes. For example, if you wish to customize the error page for 404 HTTP status codes, create a resources/views/errors/404.blade.php. This file will be served on all 404 errors generated by your application. The views within this directory should be named to match the HTTP status code they correspond to. The HttpException instance raised by the abort function will be passed to the view as an $exception variable:

    1. <h2>{{ $exception->getMessage() }}</h2>

    Laravel provides a simple abstraction layer on top of the powerful Monolog library. By default, Laravel is configured to create a log file for your application in the storage/logs directory. You may write information to the logs using the Log :

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

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

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

    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:

    Accessing The Underlying Monolog Instance

    1. $monolog = Log::getMonolog();