swayok / laravel-extended-errors

7.1 2026-11-06 13:41 UTC

Requires

• php: >=8.1
• laravel/framework: >=10.0

Requires (Dev)

• filp/whoops: ^2.15.1

MIT

• Filippov Alexander

• logging
• php
• monolog
• exception
• error
• laravel
• telegram

Published on Packagist.org on 2026-11-06 14:16 UTC

README

This package provides additional drivers (telegram and email) and log renderers for Laravel logging system. Renderers generate HTML code to be written to log files or sent to external services (slack, email, telegram).

Example of logs: screenshot_log.png

Example of exception log: screenshot_exception.png

1. Installation

Laravel <= 5.5

Add require to composer.json and run composer update

"require": {
    "swayok/laravel-extended-errors": "5.5.*",
}

Proceed using step 2 in branch laravel_up_to_5.5

Laravel 5.6+ to Laravel 9

Add require to composer.json and run composer update

"require": {
    "swayok/laravel-extended-errors": ":6.0",
}

Laravel 10+

Add require to composer.json and run composer update

"require": {
    "swayok/laravel-extended-errors": ":7.0",
}

Configuration

Service provider

Automatically added via package auto-discovery.

Renderers

HTML renderer injection into daily and single channel drivers

'single' => [
    'driver' => 'single',
    'path' => storage_path('logs/laravel.html'),
    'tap' => [\LaravelExtendedErrors\Formatter\HtmlFormatter::class],
    'level' => 'debug',
],

'daily' => [
    'driver' => 'daily',
    'path' => storage_path('logs/laravel.html'),
    'level' => 'debug',
    'days' => 7,
    'tap' => [\LaravelExtendedErrors\Formatter\HtmlFormatter::class],
], 

Drivers

All changes will be applied to 'channels' array in config/logging.php.

Telegram channel

'telegram' => [
    'driver' => 'telegram',
    'token' => env('LOG_TELEGRAM_API_KEY'),
    'chat_id' => env('LOG_TELEGRAM_CHAT_ID'),
    'proxy' => [
        'type' => env('LOG_TELEGRAM_PROXY_TYPE', 'http'),
        'host' => env('LOG_TELEGRAM_PROXY_HOST'),
        'port' => env('LOG_TELEGRAM_PROXY_PORT'),
        'user' => env('LOG_TELEGRAM_PROXY_USER'),
        'password' => env('LOG_TELEGRAM_PROXY_PASSWORD'),
    ],
    'level' => 'debug',
    'message_prefix' => env('LOG_TELEGRAM_MESSAGE_PREFIX', mb_ucfirst(env('APP_ENV', ''))),
    'bubble' => false',
    'async' => env('LOG_TELEGRAM_ASYNC', false),
    'async_queue' => env('LOG_TELEGRAM_ASYNC_QUEUE'),
]

Rendered logs and exceptions are sent as documents to provided chat_id.

Option message_prefix will wrap passed string into [] and add it in front of the message resulting in something like [Prod] *Error* Something happened. when 'message_prefix' => "Prod" and message is *Error* Something happened..

Async settings:

By default ('async' => false), sending a log message to Telegram blocks the current request until the HTTP call to the Telegram API completes. async accepts two other values:

• 'async-wait' — the request is sent asynchronously and the rest of the current request is not blocked, but the script still waits for it to finish (and runs the same fallback logic on failure) right before it terminates. No queue worker required.
• 'queue' — the send (and its fallback logic) is dispatched as a queued job instead of running in the current process at all. Requires a queue worker to be running; use async_queue to pick which queue it's dispatched to (null uses the default queue).

Proxy settings:

• proxy.type can be: http, socks4, socks5, nginx;
• proxy.user and proxy.password can be empty if proxy has no authorisation;
• proxy.host for http, socks4 and socks5 types usually is an IP address like 192.168.1.1;
• proxy.host for nginx type should be a full url like http://bot.yourdomain.com ,https://bot.yourdomain.com or http://bot.yourdomain.com:8080;
• proxy.port is not used for this type.

Proxy uses Basic Auth method to send user and password. Other auth methods are not supported right now. Make an issue if you need some (make sure CURL supports it).

Nginx vhost config to proxy requests to api.telegram.org

server {
    listen 80;
    server_name bot.yourdomain.com;
    location / {
        proxy_set_header X-Forwarded-Host $host;
        proxy_set_header X-Forwarded-Server $host;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_pass https://api.telegram.org/;
        client_max_body_size 100M;
    }
}

Email channel (probably won't work with Laravel 10+)

'email' => [
    'driver' => 'email',
    'level' => 'debug',
    'subject' => 'Server log',
    'sender' => '[e-mail]',
    'receiver' => ['[e-mail]'],
    'bubble' => false',
],

Warning: there is no limit for exceptions, and you may eventually get thousands of errors at once if you use this channels in high loaded project.

Sentry

Actually there is no channel driver for Sentry but here is quick tutorial on how to add exceptions reporting to Sentry via Handler.php:

Require sentry packages:

"require": {
    "sentry/sentry": "^1.8",
    "sentry/sentry-laravel": "^0.8.0",
}

In your app/Exception/Handler.php update report() method to look like:

public function report(Exception $exception) {
    if ($this->shouldReport($exception) && app()->bound('sentry')) {
        app('sentry')->captureException($exception, ['extra' => \LaravelExtendedErrors\Utils::getMoreInformationAboutRequest()]);
    }

    parent::report($exception);
}

To .env file add url provided by Sentry when you create a new project there. It will look like this:

SENTRY_DSN=https://[e-mail]/1

Note that there is 'extra' key used to send report to Sentry. This one stores all data from current request just like exception logs generated by HTML Renderer. This provides better understanding of what happened.

Whoops exception page replacement

To replace HTML exception pages rendered by built-in Laravel's Whoops handler with exception page rendered by this package you need to add 'replace_whoops' => true, to config/logging.php

Custom user info data collector

ExceptionHtmlRenderer prints minimal set of user info: primary key and class. To print more info you can provide your own user info collector using ExceptionHtmlRenderer::setUserInfoCollector(\Closure). Closure
receives no arguments and must return null (not authenticated) or array. Also, it is on your side how you get user object. ExceptionHtmlRenderer by default uses request()->user();