Weave Code
Advanced Logger Laravel Package
savannabits/advanced-logger
A Laravel logging package that extends Monolog with richer, structured log output, custom channels, and context-aware entries, making application debugging and auditing easier with minimal configuration.
Advanced logger
Frequently asked questions about Advanced Logger
- What does savannabits/advanced-logger actually do?
- It is a Laravel logging package that extends Monolog to produce richer, structured log output, including custom channels and context-aware log entries. The stated goal is easier debugging and auditing with minimal configuration. The material supplied with this evaluation only includes a one-line v7.0.0 release note, so verify the concrete feature list against the repository README and source before adopting.
- How do I install savannabits/advanced-logger in a Laravel app?
- Install it with Composer using composer require savannabits/advanced-logger, then check whether the package auto-discovers a service provider or requires manual registration in config/app.php. Confirm whether any config file needs to be published before use. Because the README excerpt was not provided in this evaluation, treat the exact post-install steps as something to confirm from the package docs rather than assume.
- Which Laravel versions does savannabits/advanced-logger support?
- Version 7.0.0 follows a lockstep naming convention where the package major tracks the Laravel major, so v7.0.0 targets Laravel 7. Whether it also dual-supports Laravel 6 is not documented in the supplied release note and should be read from the illuminate/* constraints in the package composer.json. If your applications run Laravel 8 or later, do not evaluate v7.0.0; look for the matching later major instead.
- Why is the package versioned like Laravel (v7.0.0)?
- The maintainer keeps the package major version consistent with Laravel major releases, so a ^7.0 constraint on this package implies Laravel 7. That collapses two upgrade axes into one and makes Composer constraints self-documenting. The tradeoff is that the package's release cadence is gated by framework releases, and the major number stops being a reliable signal of API-break severity, so plan upgrades from the changelog rather than from semver intuition.
- Is upgrading from the previous major to v7.0.0 a breaking change?
- Treat it as potentially breaking until you review the changelog and source diff. A major bump under a lockstep policy often bundles Laravel 7 compatibility together with unrelated breaking changes the maintainer batched into the release. The safe path is to bump the Composer constraint to ^7.0, resolve dependencies, run your full test suite plus any logging integration tests, and diff observed log output in staging. If any service still runs Laravel 6, confirm whether v7.0.0 is a hard cutover before scheduling the work.
- How do I configure a custom log channel with this package?
- In Laravel you would typically add a channel entry under the channels key in config/logging.php that points at the driver or handler the package provides, then select it via LOG_CHANNEL or a stack. The exact driver name, handler options, and formatter keys are package-specific and are not included in the material supplied for this evaluation, so confirm them from the repository docs. Because the package builds on Monolog, you can usually also layer standard Monolog handlers and processors on top.
- Does the package register a service provider, publish config, or ship migrations?
- This is not verified by the supplied release note, and it matters because it determines the blast radius of adoption. Check the extra.laravel.providers and aliases entries in the package composer.json to see whether a service provider is auto-discovered, and look for a publishable config file or any database migrations. A logger package normally ships no migrations, but confirm rather than assume, especially if you plan to log to a database table.
- Can I use it alongside Laravel's built-in logging instead of replacing it?
- Yes, in practice it is meant to extend rather than replace Monolog, so you can keep your existing single, daily, or stack channels and add the package's structured channels alongside them. That lets you route structured, context-aware entries to a separate destination while leaving default application logging untouched. Verify the channel driver names and formatting behavior in a staging environment before switching your default channel over.
- What are the production risks of depending on savannabits/advanced-logger?
- The largest operational risk with a lockstep-versioned package is that it can gate your own Laravel upgrade: you cannot move to the next Laravel major until this package ships its matching major. Maintenance health, maintainer count, bus factor, test coverage, and the security disclosure process are all unverified for this package. Patch and minor releases within a major should remain safe, but review each major boundary explicitly before upgrading.
- What are the alternatives to savannabits/advanced-logger?
- Laravel's built-in logging channels combined with standard Monolog handlers and processors cover most structured logging needs without an extra dependency. If your real goal is auditing rather than debugging, activity-log style packages such as spatie/laravel-activitylog target model change history more directly. Compare the feature list in this package's README against those options, and favor whichever has verifiable maintenance and a Laravel major that matches your runtime.
Weaver
How can I help you explore Laravel packages today?