salehhub/laravel-remote-logger

Send Laravel logs to a centralized remote logging server

v1.0.8 2026-02-22 23:02 UTC

Requires

• php: ^8.1
• illuminate/http: ^10.0|^11.0|^12.0
• illuminate/queue: ^10.0|^11.0|^12.0
• illuminate/support: ^10.0|^11.0|^12.0
• monolog/monolog: ^3.0

MIT

• Saleh

• logging
• remote
• laravel
• centralized

README

Send your Laravel application logs to a centralized remote logging server.

Features

• Zero config — just install, set env vars, and go
• Bearer token authentication
• Asynchronous logging (queued) to avoid slowing down requests
• Automatic retry on failure (3 attempts with backoff)
• Configurable timeout and SSL verification
• Fallback to local logging on failure

Installation

composer require salehhub/laravel-remote-logger

The package auto-registers via Laravel's package discovery.

Configuration

1. Add Environment Variables

REMOTE_LOGGER_URL=https://your-logging-server.com/api/logs
REMOTE_LOGGER_API_KEY=your-api-key
REMOTE_LOGGER_APP_NAME=MyApp

All available environment variables:

Variable	Default	Description
REMOTE_LOGGER_URL	http://localhost:8000/api/logs	Remote server endpoint
REMOTE_LOGGER_API_KEY	null	Bearer token for authentication
REMOTE_LOGGER_APP_NAME	APP_NAME	Application identifier
REMOTE_LOGGER_LEVEL	debug	Minimum log level to send
REMOTE_LOGGER_ASYNC	true	Send logs via queue
REMOTE_LOGGER_QUEUE	null	Queue name (null = default queue)
REMOTE_LOGGER_VERIFY_SSL	true	Verify SSL certificates
REMOTE_LOGGER_TIMEOUT	5	HTTP request timeout in seconds

2. Set as Default Log Channel

LOG_CHANNEL=remote

The remote channel is auto-registered by the package. No need to edit config/logging.php.

3. Queue Setup (for async logging)

php artisan queue:work

Usage

use Illuminate\Support\Facades\Log;

Log::info('User logged in', ['user_id' => 123, 'category' => 'Auth', 'subcategory' => 'Login']);
Log::error('Payment failed', ['order_id' => 456, 'category' => 'Payments', 'subcategory' => 'Stripe']);
Log::warning('High memory usage detected', ['category' => 'System']);

Global Context (Optional)

You can set a global category or subcategory that applies to all logs in the current request or job. This is useful for assigning a broad category to an entire request cycle.

use RemoteLogger\Facades\RemoteLogger;

// At the beginning of a request or job
RemoteLogger::setContext('Billing', 'StripeProvider');

// Or separately
RemoteLogger::setCategory('Billing');
RemoteLogger::setSubcategory('StripeProvider');

Global settings (via RemoteLogger facade) will always take precedence over values provided in the log context.

Remote Server Payload

Your server should accept POST requests with this JSON structure:

{
    "application": "MyApp",
    "environment": "production",
    "level": "info",
    "message": "User logged in",
    "category": "Auth",
    "subcategory": "Login",
    "context": {"user_id": 123},
    "logged_at": "2024-02-08 10:30:00"
}

The request includes an Authorization: Bearer <api_key> header when REMOTE_LOGGER_API_KEY is set.

Publishing Config

php artisan vendor:publish --tag=remote-logger-config

Synchronous Mode

Set REMOTE_LOGGER_ASYNC=false to send logs synchronously (not recommended for production).

License

MIT