- What is muhdfaiz/laravel-tail-db and what does it do?
- Laravel Tail DB is a Laravel package that monitors database activity in real time. It streams executed queries and database events through an Artisan command so you can watch interactions as they happen. It is aimed primarily at development and debugging workflows rather than production monitoring.
- How do I install laravel-tail-db with Composer?
- Install it as a development dependency using Composer with the package name muhdfaiz/laravel-tail-db. Run composer require muhdfaiz/laravel-tail-db from your Laravel project root. If the package does not use auto-discovery, register its service provider in your application config as described in the README.
- Which Artisan command do I run to tail database queries?
- The package exposes an Artisan command that starts streaming queries and database events to your terminal. Check the repository README or run php artisan list to confirm the exact command signature for your installed version. You typically run it in one terminal while exercising the application in another.
- Does laravel-tail-db support dynamically set database names and multi-tenant apps?
- Version 1.1.3 specifically fixed an error that occurred when the database name was set dynamically by the application. That makes it more viable for multi-tenant and per-request database setups where the connection name is resolved at runtime. Validate it against your own tenancy package before relying on it, since the release note does not document the full scope of the fix.
- Which Laravel and PHP versions does this package support?
- The supported version matrix is not stated in the supplied package metadata, so confirm it in the repository composer.json before installing. The 1.1.3 release indicates active maintenance at that point, but the constraint ranges vary by release. Pin a version that matches your Laravel and PHP runtime.
- Should I run laravel-tail-db in production?
- It is designed as a development debugging aid that streams queries in real time, so treat it as a local and staging tool rather than a production monitoring system. Running it against production can expose sensitive query data and adds overhead to your connection path. Use established APM or logging tools for production database observability.
- Will tailing queries slow down my application?
- Any listener attached to the database query events adds work per query, and the impact depends on query volume and how output is buffered. Real-time streaming to a terminal is best used in short debugging sessions. Disable or remove the package from non-development environments to avoid unnecessary overhead.
- Does laravel-tail-db work with php artisan config:cache?
- Version 1.1.3 addressed a failure caused by runtime database names, which is the same class of problem that config caching can trigger. Whether the cached configuration path is explicitly supported and tested is not confirmed in the available information. If you deploy with config:cache and dynamic connections, test the package in that configuration before adopting it.
- How is laravel-tail-db different from Laravel Telescope or Debugbar?
- Telescope and Debugbar bundle broad request, exception, and query inspection into a larger dashboard or toolbar. Laravel Tail DB is narrower, focusing on streaming queries and database events live through an Artisan command. It suits developers who want a lightweight terminal view rather than a full debugging suite.
- What should I verify before adopting this package?
- Check whether a regression test covers the dynamic database name scenario fixed in 1.1.3, since that class of bug tends to return. Review the changelog, supported Laravel and PHP ranges, open issues, and release cadence to gauge maintenance health. Also confirm how the package behaves alongside other tools that modify database configuration during boot.