- How do I install kitloong/laravel-app-logger in a Laravel application?
- Install it with Composer using composer require kitloong/laravel-app-logger. Then publish the config file and migrations, register the package middleware, and run php artisan migrate. Most teams should expect roughly half a day to a day to get a first non-production deployment validated against their actual PHP, database, and queue drivers.
- Which Laravel versions does laravel-app-logger support?
- Version 1.3.0 adds Laravel 13 support, while earlier releases covered Laravel 10 through 12. Check the Composer constraint in the package's composer.json before upgrading, because the release may have widened or narrowed the supported range. If you are staying on an older major, pin to ^1.2.4 when the newer release drops support for it.
- Do I need to run migrations for laravel-app-logger?
- Yes. The package ships migrations for its database log table, so you need to publish and run them with php artisan migrate. On existing installations, confirm migration idempotency before deploying, since new columns and indexes are the usual breakage point during package upgrades.
- Does laravel-app-logger require middleware registration?
- Yes. The package uses request-level middleware plus a persistence layer to record application activity and errors. Register the middleware in your HTTP kernel or bootstrap configuration the same way you would any other Laravel middleware. It sits beside your domain code rather than inside it, so there is no service container rewiring or domain model change.
- Is laravel-app-logger safe to use in production performance-wise?
- The package writes log rows to your database, which adds write amplification and latency on the request path under peak traffic. Confirm whether inserts are synchronous by default and whether a queue or async option exists. If not, use sampling and retention deliberately, and monitor database load before enabling it on high-traffic production endpoints.
- How do I redact passwords and PII from laravel-app-logger entries?
- Request bodies, headers, and query strings commonly contain credentials and personal data, so redaction must be configured and verified before production, not after. Review the published config for header, body, and query parameter controls and confirm whether they are default-on or opt-in. Test the redaction rules in staging with realistic payloads so sensitive values never reach the log table.
- How do I stop the laravel-app-logger table from growing too large?
- Per-request log rows grow with traffic, so plan for sampling, a retention or pruning command, and table partitioning. Check whether the package supports a separate database connection so log writes do not compete with application queries. Without these controls, the log table can become the operational problem it was meant to diagnose.
- Does laravel-app-logger work with Laravel Octane and multi-tenant applications?
- Validate Octane and Swoole compatibility in staging, especially if the package buffers any log data in long-lived worker memory. In multi-tenant applications, confirm that rows are scoped to the correct tenant and that the configured database connection is appropriate. These are stack-specific concerns rather than guarantees, so test against your actual deployment setup.
- What is the difference between laravel-app-logger and Laravel Telescope or built-in logging?
- laravel-app-logger is a lightweight database-backed recorder for application activity and errors, not a full APM, metrics, or tracing platform. Laravel's built-in logging writes flat files, while Telescope is a broader debugging assistant with a viewer. If your organisation already centralises logs in ELK, Datadog, or CloudWatch, this package adds a second, weaker log surface, so treat it as a tactical diagnostic aid.
- Is kitloong/laravel-app-logger actively maintained and risky to depend on?
- It is a small open-source package with a single maintainer, so bus factor and response time to security issues are real considerations. The v1.3.0 release adding Laravel 13 support is a positive maintenance signal but not a functional change. The package has low architectural coupling and a small blast radius, so pinning versions and scheduling upgrades alongside framework upgrades keeps the dependency manageable.