Download the PHP package atmos/laravel-db-sentinel without Composer

DB Sentinel for Laravel

Laravel DB Sentinel is a smart database query monitoring and optimization tool for Laravel 7+. It helps Laravel applications track, analyze and optimize database behavior with insights on slow or inefficient queries and actionable performance feedback.

⚠️ Beta Version
This package is currently in Beta. Expect frequent updates and potential breaking changes until we reach version 1.0.0. Please report any issues or bugs on the GitHub repository.

✨ Features

• 📊 Quick Dashboard — A clean UI to visualize your database status.
• 🔍 Query Monitoring — Automatically capture and log all database queries executed by your application.
• 🐢 Slow Query Detection — Highlight queries that exceed a configurable execution threshold.
• 📈 Performance Insights — Collect statistics like query counts, total time spent, and slow query summaries.
• 🧪 Developer-Friendly Output — Easy logs or debug output to help you optimize during development.
• 🛡️ Built-in Authorization: — Restrict access to specific users via User IDs.
• ⚙️ Configurable & Lightweight — Enable or disable features via config — no performance impact in production.

📦 Installation

Install Laravel DB Sentinel via Composer:

⚠️ Important: Run Migrations

After installing the package, you must run:

Laravel Auto-Discovery

This package supports Laravel's package auto-discovery, so no manual registration is required.

If auto-discovery is disabled, manually register the service provider in config/app.php:

🔧 Publishing Package Resources

Laravel DB Sentinel allows you to publish its resources so you can customize them inside your application.

📄 Publish Configuration File

Publish the configuration file to config/db-sentinel.php:

🎨 Publish View Files

If the package provides Blade views, publish them with:

Published views will be located in:

You can safely modify these views without affecting the core package.

💡 Tip: You can run php artisan vendor:publish without arguments to interactively choose which resources to publish.

⚙️ Configuration

DB Sentinel is designed to work out of the box, but you can customize its behavior using the following environment variables in your .env file.

🔌 General & Storage

⚡ Performance & Scope

🖥️ Dashboard & Security

📝 Example .env Setup

⚠️ Important Logic & Security Notes

🔄 Connection Precedence

When configuring your monitoring scope, please note the following hierarchy:

• DB_SENTINEL_IGNORED_CONS always takes precedence.
• If a connection is listed in both "allowed" and "ignored," it will be ignored.
• Ensure your primary connection is not accidentally added to the ignored list.

🔒 Dashboard Access

[!CAUTION] Be cautious when setting DB_SENTINEL_USER_IDS. This variable controls who can view your database performance metrics and raw SQL queries.

• Ensure you only input the numeric IDs of trusted administrators.
• If left empty while DB_SENTINEL_DASHBOARD is true, access will depend solely on your auth middleware, which may be too permissive depending on your app's setup.

🧹 Pruning

Auto-Pruning

By default, DB Sentinel schedules a daily cleanup of old logs.

Configuration

You can control this behavior in your .env:

[!TIP] If you set DB_SENTINEL_SCHEDULE_ENABLED=false, the package will not register the task. You can then manually add php artisan db-sentinel:prune to your own Scheduler at a specific time that suits your server load.

🧹 Manual Pruning

If you want to clear old logs immediately without waiting for the automated scheduler, you can run the built-in Artisan command.

Usage

Run the following command in your terminal: