- What is bilias/rqwatch used for in a Laravel application?
- bilias/rqwatch is described as a lightweight Laravel package for watching incoming HTTP requests. It captures request metadata such as method, path, status, and timing through middleware, so you can inspect traffic and diagnose issues without building custom logging. It is intended for developers who need quick visibility into route traffic rather than a full observability platform.
- How do I install bilias/rqwatch in a Laravel app?
- Installation is normally done with Composer using composer require bilias/rqwatch, followed by publishing any package config and registering the middleware. Because package distributions can vary, confirm the exact service provider and middleware alias in the repository README before deploying. After installation, run your migrations if the package ships a storage table.
- Which Laravel versions does bilias/rqwatch support?
- The supplied overview does not list explicit Laravel or PHP version constraints. Check the package's composer.json for illuminate/support, PHP, and dependency requirements before adding it to an existing application. For production, pin a release that matches your Laravel major and test the middleware in staging.
- How do I configure which requests rqwatch captures?
- Use the package's configurable include and exclude rules to focus capture on relevant routes and ignore noise. Typical exclusions are health checks, asset requests, webhooks, and high-volume API endpoints. Keep the rules narrow so stored data stays useful and middleware overhead stays low.
- Does rqwatch record request bodies or only metadata?
- The overview describes metadata such as method, path, status, and timing; it does not state that request bodies or sensitive payloads are captured. Treat it as a traffic-diagnosis tool and verify behavior before enabling it on login, payment, or other sensitive routes. If body capture exists, apply redaction and retention controls.
- How does pruning work for stored request data?
- The package includes optional pruning to keep stored request data manageable. Configure the retention window and schedule the package's pruning command if one is provided; otherwise add a scheduled job to delete old records from its storage table. Set retention based on debugging needs and data sensitivity.
- Can I run rqwatch in production without slowing requests?
- Middleware-based capture adds some overhead, so scope it with include/exclude rules and avoid capturing very high-traffic routes unless needed. Store captured data in a dedicated table or connection, and monitor query and write volume. Test under realistic load in staging before enabling it broadly in production.
- How do I test that rqwatch middleware is recording requests?
- Write Laravel HTTP tests that hit representative routes with the middleware enabled, then assert the expected records exist. Use RefreshDatabase or a test database, and override package config in your test case so include/exclude rules are deterministic. Also test that excluded routes do not create records.
- Is bilias/rqwatch a Laravel HTTP request watcher or a Redis queue watcher?
- The overview frames bilias/rqwatch as a Laravel middleware package for watching incoming HTTP requests, while some supplied snippets mention Redis queues or a standalone Rspamd/Postfix service. Those descriptions point to different architectures, so confirm the repository, version, and installation method before adopting it. If you need queue visibility, verify that the package actually provides it.
- What should I check before choosing bilias/rqwatch over alternatives?
- Compare it with Laravel Telescope, Debugbar, structured request logging, and custom middleware based on whether you need local diagnostics or production traffic analysis. Check the repository's recent commits, open issues, Laravel compatibility, and security disclosures before committing. Because the package is lightweight, be prepared to fork or replace it if maintenance stalls.