This package is abandoned and no longer maintained. The author suggests using the barryvdh/laravel-debugbar package instead.

A profiler for Laravel 4

Installs: 23 586

Dependents: 0

Suggesters: 0

Security: 0

Stars: 123

Watchers: 12

Forks: 28

v1.0.0 2013-08-08 12:16 UTC

This package is not auto-updated.

Last update: 2016-01-29 19:10:48 UTC


This project is abandoned at 23 September 2013. Developers who want to be free to continue on own fork. I personally started using and support a much better interface with the barryvdh/laravel-debugbar.


A profiler for Laravel 4. Backend based on sorora/omni, frontend based on loic-sharma/profiler, some features inspired by papajoker/profiler, some features original by myself.



  • Environment info
  • Current controller/action info
  • Routes
  • Log events
  • SQL query log with syntax highlighting
  • Total execution time
  • Total memory usage
  • Includes files (I don't think this is really needed)
  • All variables passed to views
  • Session variables
  • Laravel auth variables (Need to test)
  • Sentry auth variables


To add Profiler to your Laravel application, follow these three steps:

Add the following to your composer.json file:

"juy/profiler" : "dev-master"

Then, run composer update or composer install if you have not already installed packages.

Add the below line to the providers array in app/config/app.php configuration file (add at the end):


Add the below line to the aliases array in app/config/app.php configuration file (add at the end):

'Profiler' => 'Juy\Profiler\Facades\Profiler',


You will want to run the following command to publish the config to your application, otherwise it will be overwritten when the package is updated.

php artisan config:publish juy/profiler

Set this option to FALSE to disable the profiler. By default, it is NULL, which makes the profiler refer to the app debug option in config/app.php.

// config.php
'profiler' => NULL

If you wish to disable the profiler during your application, just do:

Config::set('profiler::profiler', FALSE);

// or


Note:: This will only disable the output, it will still do it's background listening but will not output it to the browser.


Custom Timers

To start a timer, all you need to do is:

Profiler::start('my timer key');

To end the timer, simply call the end function like so:

Profiler::end('my timer key');


Profiler utilizes Laravel's built in logging system and captures logged events. To log events, you can do (as you would with Laravel) any of these:

Log::debug('Your message here');
Log::info('Your message here');
Log::notice('Your message here');
Log::warning('Your message here');
Log::error('Your message here');
Log::critical('Your message here');
Log::alert('Your message here');
Log::emergency('Your message here');

These are color-coded in the Logs part of the profiler – colors may change in future to more accurately reflect the log type.


This project is open-sourced software licensed under the MIT license.