Weave Code
Log Laravel Package
scafera/log
Scafera Log is a logging package for Laravel and PHP applications, offering a simple, configurable way to capture, format, and manage application logs. It fits into Laravel's logging stack and supports custom handlers for debugging and production monitoring.
Structured logging for the Scafera framework
Frequently asked questions about Log
- How do I install Scafera Log in a Laravel application?
- Install the package with Composer using composer require scafera/log. Then follow the package README for any service provider registration or configuration publishing steps. Because it follows Laravel logging conventions, most configuration will live alongside your existing config/logging.php channels.
- Does Scafera Log replace Laravel's native logging system?
- No. Scafera Log extends Laravel's native logging stack rather than replacing it. It provides a consistent PSR-3-compatible interface and routes structured events to configured destinations. You can adopt it without rewriting all existing logging calls at once.
- Is Scafera Log PSR-3 compatible?
- Yes. The package provides a drop-in LoggerInterface implementation for PSR-3 interoperability. That means you can type-hint the standard logger interface in your own classes and keep logging code portable. Check the README for the exact binding or injection setup in Laravel.
- Can Scafera Log send logs to multiple destinations?
- Yes. It supports multiple drivers, including file, stream, and custom handlers, behind one API. Destinations are selected through configuration-driven channels. This lets you keep local file logging while also routing events to a stream or custom production handler.
- How does context-aware logging work in Scafera Log?
- Scafera Log lets you attach structured context to log records, such as request IDs, user data, and custom metadata. That context travels with the event through the configured driver. This is useful for correlating requests and adding operational detail without changing every log message.
- How do I configure Scafera Log channels?
- Configure channels using Laravel's config/logging.php conventions, as described by the package. Each channel can point to a file, stream, or custom handler behind the shared logger API. Keep environment-specific settings in your normal Laravel configuration and avoid hard-coding production destinations.
- How can I test logs in unit tests with Scafera Log?
- The package includes an in-memory logger intended for assertions in unit tests. You can capture emitted records and assert on messages, levels, and context without writing to real files. This keeps logging tests fast and isolated from filesystem or stream side effects.
- Which Laravel and PHP versions does Scafera Log support?
- The provided package overview does not list exact Laravel or PHP version ranges. Check the package composer.json and README for the supported compatibility matrix before installing or upgrading. Confirm the range against your application's framework and PHP versions, especially before a major Laravel upgrade.
- What should I consider before using Scafera Log in production?
- Treat it as part of your application's logging infrastructure and verify file permissions, log rotation, and destination availability. Avoid placing sensitive values in context metadata unless your configured drivers and retention policies are appropriate. Also test the production channel configuration in staging so missing paths or custom handlers fail visibly.
- How does Scafera Log compare with Laravel logging or Monolog alternatives?
- Scafera Log is a lightweight layer on Laravel's logging stack, so it is closest to using Laravel channels and Monolog directly. Choose it when you want a simple config-driven API for file, stream, and custom handlers plus PSR-3 interoperability and an in-memory test logger. If you need a broad ecosystem of existing handlers, Laravel's native Monolog setup may already be sufficient.
Weaver
How can I help you explore Laravel packages today?