Weave Code
Laravel Logging Laravel Package
eur-rsm/laravel-logging
A Laravel logging package from eur-rsm that helps streamline log configuration and management within Laravel applications. It integrates with Laravel’s logging system to support consistent, maintainable application logs and a cleaner, more organized logging setup across environments.
Enrich laravel logging
Frequently asked questions about Laravel Logging
- What does eur-rsm/laravel-logging do?
- eur-rsm/laravel-logging is a Laravel package intended to enrich application logs, most likely by adding structured context through Monolog processors, channel taps, or a custom formatter. The repository description is only 'Enrich laravel logging', so confirm the exact fields it adds before adopting it. Architecturally it should integrate additively with Laravel's logging stack rather than replacing the Log facade.
- How do I install eur-rsm/laravel-logging in a Laravel application?
- The expected path is composer require eur-rsm/laravel-logging, followed by publishing any package config file if the service provider supports it. Laravel package auto-discovery may register the provider automatically, but verify that in the source. The provided context does not confirm Packagist availability, so you may need a VCS or path repository instead.
- Which Laravel and PHP versions does eur-rsm/laravel-logging support?
- The provided evaluation does not list declared constraints, so check the package composer.json for php and illuminate/support or illuminate/* requirements. Laravel 11 moved to Monolog 3, which changed processor and handler contracts, so version support matters. Test against your exact Laravel and PHP matrix before scheduling a spike.
- Does eur-rsm/laravel-logging support Monolog 3 and Laravel 11?
- This is not confirmed in the available context. Monolog 3 changed record and handler contracts, so any processor or tap must be explicitly compatible. Inspect composer.json and run a staging test on Laravel 11 before relying on it.
- Is eur-rsm/laravel-logging on Packagist and safe to require?
- Packagist availability is not confirmed by the provided context, and the package has zero stars and zero dependents. That means there is no production corpus, issue history, or independent security review to rely on. Prefer reviewing the source and pinning a version, or vendor it through a VCS path repository, before granting it execution in every request and queue worker.
- Is eur-rsm/laravel-logging a Monolog processor, a tap, or a LogManager override?
- The evaluation identifies processors, channel taps, and custom formatters as the normal seams, and warns that a LogManager override is a meaningful upgrade hazard. The provided context does not state which approach this package uses. Inspect the service provider and source to confirm before adopting it.
- What should I check before using eur-rsm/laravel-logging in production?
- Review the license, changelog, test suite, CI configuration, and static-analysis baseline, and confirm the package is actually installable from Packagist. Check whether enrichment is global or per-channel, because global registration changes output for every existing channel and downstream parser. Also verify redaction behavior and whether it serializes request bodies or user models into every log record.
- Does eur-rsm/laravel-logging work in queue workers and scheduled commands?
- That depends on whether the enrichment reads request-scoped state such as the session, auth guard, or request ID. In queue workers and scheduled commands those values may be absent, so the code must be null-safe. Test the package in CLI context and confirm it does not break when no HTTP request exists.
- Can I use Laravel's Log::withContext() instead of eur-rsm/laravel-logging?
- Yes. Laravel already provides Log::withContext(), Context facade integration, and documented processor and tap patterns, and a short custom processor plus middleware can add request ID, user ID, tenant, and correlation ID. The package is only worth adopting if it provides verified value beyond those first-party primitives. With zero dependents, that value proposition is unproven.
- How do I configure which channels get enriched by eur-rsm/laravel-logging?
- The provided context does not document the configuration surface, but likely options are a publishable config file and taps in config/logging.php. Confirm whether registration is global or per-channel before enabling it. Prefer per-channel enrichment so existing log parsers and downstream consumers are not surprised.
Weaver
How can I help you explore Laravel packages today?