Weave Code
Logs Laravel Package
litermi/logs
litermi/logs is a Laravel/PHP package that simplifies application logging with configurable log handling and easy integration into Laravel projects. Use it to capture, organize, and review runtime events for debugging and monitoring.
package to log routines and sql query
Frequently asked questions about Logs
- How do I install litermi/logs in a Laravel application?
- Install it with composer require litermi/logs. Laravel package auto-discovery should register the service provider, and you may optionally publish a config file with php artisan vendor:publish. Before adopting it, check the declared PHP and illuminate/* constraints, because the repository has no release history to confirm version support.
- Does litermi/logs support Laravel 11 and PHP 8.x?
- The provided context does not state the supported PHP or Laravel versions, and no tagged release history is available. Inspect composer.json for PHP, illuminate/*, and Laravel major-version constraints rather than assuming Laravel 11 support. A package written for Laravel 8 may silently misbehave on newer versions.
- What is the difference between litermi/logs and Laravel Telescope?
- laravel/telescope already provides query watching, request tracing, and slow-query detection, while litermi/logs focuses on logging routines and SQL queries. The overlap is substantial, so litermi/logs must justify itself on smaller footprint, production safety, or log-format ergonomics. barryvdh/laravel-debugbar is another local-debugging alternative.
- Does litermi/logs log SQL query bindings and could that expose sensitive data?
- Query logging can capture bound parameters, which may include passwords, tokens, session identifiers, and PII. The context does not confirm whether litermi/logs redacts or truncates parameters or whether redaction is configurable per key. Treat this as the largest risk and verify redaction in code before any non-local deployment.
- Is litermi/logs safe to use in production?
- Be cautious: the package has zero stars, zero dependents, and no production evidence beyond its author. Query logging raises sensitive-data, overhead, and recursion risks, and there is no stated security disclosure or deprecation policy. Prefer using it as a reference implementation or validating it thoroughly in a non-production environment.
- How does litermi/logs capture SQL queries: DB::listen, query log, or middleware?
- The context does not specify whether litermi/logs hooks DB::listen, Laravel's query log, or middleware. Inspect the service provider and listener code to confirm the mechanism and check behavior under Octane, queued jobs, and multiple database connections. A global DB::listen callback runs on every query, so overhead and recursion guards matter.
- Does litermi/logs protect against recursion when logging to the database?
- It is not confirmed whether litermi/logs includes recursion protection for database-backed log channels. If the package writes logs to the database, that write emits a query that the listener could capture, creating a loop. Verify the guard in code or route logs to a file channel before enabling database logging.
- Can I limit or sample query logging in litermi/logs to reduce overhead?
- The context does not confirm whether query capture is sampling-capable or all-or-nothing. A global DB::listen callback executes on every query, so query-heavy endpoints may see measurable overhead. Check the config for sampling or exclusion options; otherwise implement your own listener with sampling.
- What are the alternatives to litermi/logs for routine and SQL query logging in Laravel?
- Consider laravel/telescope for query watching and request tracing, barryvdh/laravel-debugbar for local debugging, and Monolog channels for structured logging. A first-party DB::listen listener of roughly 50 lines can reproduce query tracing with your own redaction and sampling rules. That approach avoids adding an unproven dependency.
- Is litermi/logs actively maintained and does it have a stable release?
- The repository has a single owner, zero stars, zero dependents, and no tagged release or CHANGELOG described in the context. No deprecation policy, security disclosure path, or support commitment is stated. Treat maintenance as uncertain and review the license and code before commercial use.
Weaver
How can I help you explore Laravel packages today?