Skip to content
Laravel package to find performance bottlenecks in your laravel application.
Branch: master
Clone or download
Sarfraz Ahmed
Sarfraz Ahmed fixes #9, fixes #8, fixes #7
Latest commit b950e05 Feb 12, 2020


Type Name Latest commit message Commit time
Failed to load latest commit information.
src fixes #9, fixes #8, fixes #7 Feb 12, 2020
tests tests (wip) Feb 9, 2020
.editorconfig first commit Dec 16, 2019
.gitattributes first commit Dec 16, 2019
.gitignore update Jan 26, 2020 first commit Dec 16, 2019
composer.json fixes #6 Feb 11, 2020
phpunit.xml update Jan 26, 2020
screenshot.png update Jan 26, 2020

Software License Latest Version on Packagist Total Downloads

Laravel Meter

Laravel Meter monitors application performance for different things such as requests, commands, queries, events, etc and presents results in tables/charts. Think of it like Laravel Telescope but for performance monitoring.


  • PHP >= 7.3
  • Laravel 5.5+ | 6


  • Requests
  • Queries
  • Commands
  • Events
  • Schedule
  • CPU Load
  • Disk Space
  • Server Memory
  • HTTP Connections


Main Window


Install via composer

composer require sarfraznawaz2005/meter

Publish package's config file by running below command:

php artisan vendor:publish --provider="Sarfraznawaz2005\Meter\MeterServiceProvider"

It should publish config/meter.php config file and migration file.

Now run php artisan migrate command to create meter_entries database table.


Enable Meter in config/meter.php and setup any other options as needed. Meter UI will be visible at path config you set.

By default Meter monitors:

  • Requests
  • Queries
  • Commands
  • Events
  • Schedule

To monitor server stuff:

  • CPU Load
  • Disk Space
  • Server Memory
  • HTTP Connections

You should use meter:servermonitor command. Schedule it in Laravel's console kernel file accordingly:

// app/Console/Kernel.php
protected function schedule(Schedule $schedule)
    $schedule->command('meter:servermonitor')->hourly(); // or daily


You can use username and password config options to setup basic HTTP authentication for Meter interface to be accessed. Once setup, user should provide correct username and password to access Meter page(s).

Alternatively, you can use middleware config option to apply your own auth middleware, etc

Ignoring Things

You can use ignore_paths and ignore_commands config options to ignore desired pages or commands from being monitored by Meter.

Data Pruning

You need to periodically remove meter data otherwise your database will turn big quickly. To prune meter data, you can setup prune command in Kernel file:

// or
$schedule->command('meter:prune --days=7')->daily();


PRs are welcome. Thanks


If you discover any security related issues, please email instead of using the issue tracker.



Please see the license file for more information.

You can’t perform that action at this time.