Weave Code
App Logger Laravel Package
roadrunner-php/app-logger
Send log messages to RoadRunner with this PHP 8.1+ package. Create a Logger over an RPC connection and call debug, info, warning, error, or log to route messages to RoadRunner’s logger or stderr. Simple YAML config.
roadrunner-php/app-logger sends application log messages directly to the RoadRunner server over RPC, so output lands in RoadRunner's configured log channels instead of local files. Define an app channel in your RoadRunner logs config, create a RoadRunner\Logger\Logger from a Spiral\Goridge\RPC instance, and start writing—no extra handlers required.
- Logger mapping:
debug,info,warning, anderrorroute to RoadRunner's own loggers - Raw stderr output via the
log()method for custom formatting - Flexible RPC setup: from a TCP address, globals, or environment variables
- Centralized configuration: channels and levels managed in RoadRunner YAML
- PHP 8.1+ with PHPUnit, Psalm, and Codecov coverage
Frequently asked questions about App Logger
- How do I install roadrunner-php/app-logger in a Laravel application?
- Install it with Composer using composer require roadrunner-php/app-logger. The package is a RoadRunner-specific RPC logger, so you also need a running RoadRunner server with RPC enabled and a logs channel configured. In Laravel, wire the RoadRunner Logger into your bootstrap or service provider where you want application logs sent to RoadRunner rather than only to Laravel's default Monolog handlers. If you are migrating from a prior package name, confirm any alias and update Composer manifests and imports.
- What PHP version does roadrunner-php/app-logger require?
- The README lists PHP 8.1 or newer as the requirement. Check the current Composer constraints on Packagist for the exact version you install, because release notes and dependency metadata can vary. Older Laravel applications should verify framework and dependency compatibility before adding the package.
- Does roadrunner-php/app-logger implement PSR-3 or replace Laravel's logging stack?
- The documented API is a RoadRunner Logger class with debug, info, warning, error, and log methods, not a stated PSR-3 implementation. It sends messages to RoadRunner over RPC, with log mapped to stderr and the other methods mapped to RoadRunner's logger. Treat it as a RoadRunner-specific logging component rather than a drop-in replacement for Laravel's Monolog or PSR-3 stack unless you add your own adapter.
- How do I configure RoadRunner RPC for roadrunner-php/app-logger?
- Enable an RPC listener in the RoadRunner configuration, for example tcp://127.0.0.1:6001, and define an application log channel such as app with an appropriate level. Then create a RoadRunner Logger using an RPC connection from RPC::create, RPC::fromGlobals, or RPC::fromEnvironment. In Laravel, keep that connection setup in a bootstrap or service-provider path that runs inside the RoadRunner worker.
- What logging methods are available in roadrunner-php/app-logger?
- The package provides debug, error, info, and warning methods that map to RoadRunner's logger. It also provides a log method that writes to RoadRunner stderr. These methods let application code send log messages over RPC without directly writing to files or standard output.
- Does roadrunner-php/app-logger support Laravel Octane, and which Laravel versions can use it?
- The package does not document Laravel-specific version constraints; it targets PHP 8.1+ and RoadRunner RPC, so Laravel compatibility depends on running your Laravel version under RoadRunner. It can fit Laravel Octane deployments that use the RoadRunner server, but Octane-specific integration is not documented. You may need custom bootstrap or configuration to create the RPC logger and route logs through it, and you should test worker lifecycle behavior in staging.
- Is roadrunner-php/app-logger compatible with RoadRunner v2 and v3?
- The release context notes RoadRunner v3 support, while the README does not document a RoadRunner v2 compatibility guarantee. If you are still on RoadRunner v2, verify the package version and RPC behavior before upgrading. For new deployments, target RoadRunner v3 and confirm the RPC endpoint and log channel configuration.
- How do I test roadrunner-php/app-logger in a Laravel application?
- Run a RoadRunner instance with RPC and an app log channel enabled, then exercise the debug, info, warning, error, and log methods from a test route or command. Assert that messages reach RoadRunner's output and that stderr logging behaves as expected. Also test worker restarts and failure cases, because RoadRunner keeps PHP workers alive between requests.
- What are alternatives to roadrunner-php/app-logger for Laravel logging?
- Laravel's default Monolog and PSR-3 logging stack remains the standard choice for application logs and supports many handlers. If you run RoadRunner, roadrunner-php/app-logger is a specialized RPC option for sending logs to the RoadRunner server. You can also use a custom Monolog handler that forwards to RoadRunner if you need Laravel logging semantics.
- Is roadrunner-php/app-logger production-ready and well maintained?
- The public repository, Packagist package, PHPUnit and Psalm badges, and RoadRunner v3 support are positive maintenance signals. However, support appears to be GitHub issue and commit based rather than vendor-backed, and details such as log rotation, high-throughput failure handling, and security response are not confirmed in the README. Assign an internal owner to track Composer upgrades and RoadRunner compatibility before production use.
Weaver
How can I help you explore Laravel packages today?