Master Laravel Exception Handling: Custom Handlers, HTTP Errors, and Logging

Overview

Exception handling is a critical part of web application development, ensuring that unexpected errors are managed gracefully and users receive meaningful responses. Laravel offers a powerful exception handling system that lets developers control error reporting and rendering.

Understanding Laravel Syntax

In Laravel, exceptions are instances of the Exception class or its subclasses, providing detailed error information. The framework centralises handling in the App\Exceptions\Handler class, where you can customise how exceptions are reported and presented.

Exception Handler

The Handler class captures and processes exceptions. Its render() method determines the HTTP response for a given exception. Example implementation:

public function render($request, Throwable $exception)
{
    if ($exception instanceof CustomException) {
        return response()->view('errors.custom', [], 500);
    }

    return parent::render($request, $exception);
}

This code checks whether the exception is a CustomException. If so, it returns a custom error view; otherwise, it falls back to Laravel's default rendering.

Custom Exception Class

Creating custom exception classes helps organise different error types. A simple custom exception looks like this:

namespace App\Exceptions;

use Exception;

class CustomException extends Exception
{
    // Additional properties or methods can be added here
}

You can throw it anywhere in your code:

throw new CustomException('This is a custom exception.');

Handling HTTP Errors

Laravel provides the abort helper to throw HTTP exceptions with specific status codes and messages. Example:

abort(404, 'Resource not found.');

This generates an HttpException with a 404 status and the supplied message.

Database Exception Handling

When working with databases, you must catch query‑related errors. The following snippet demonstrates catching a QueryException, logging the error, and returning a JSON response:

use Illuminate\Support\Facades\DB;
use Illuminate\Database\QueryException;

try {
    DB::table('users')->insert([
        'name' => 'John Doe',
        'email' => '[email protected]',
    ]);
} catch (QueryException $e) {
    // Handle the database exception
    Log::error($e->getMessage());
    return response()->json(['error' => 'Database error'], 500);
}

Validation Exception Handling

Laravel's validation system throws exceptions on failure. In a controller you can validate input as follows:

public function store(Request $request)
{
    $validatedData = $request->validate([
        'name' => 'required|string|max:255',
        'email' => 'required|email|unique:users',
    ]);

    // Your logic here
}

If validation fails, Laravel automatically redirects back with error messages; you can also handle the exception manually to customise the response.

Logging Exceptions

Recording exceptions is essential for debugging and monitoring, especially in production. Laravel’s Log facade makes this straightforward:

use Illuminate\Support\Facades\Log;

try {
    // Your code here
} catch (\Exception $e) {
    // Log the exception
    Log::error($e->getMessage());
    // Additional handling logic
}

Logging provides insight into runtime issues and aids in diagnosing problems.

For more details, refer to the official Laravel error handling documentation at https://laravel.com/docs/10.x/errors.