A profiler for Laravel 4. Backend based on sorora/omni, fronted based on loic-sharma/profiler, some features inspirated from papajoker/profiler, some feature original by myself.
- Environment info
- Current controller/action info
- Routes
- Log events
- SQL Query Log with syntax highlighting
- Total execution time
- Custom "checkpoints", see this section
- Total memory usage
- Includes files (I think not realy need this)
- All variables passed to views
- Session variables
- Laravel auth variables (Need test)
- Sentry auth veriables
To add Profiler to your Laravel application follow this 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 below to the providers array in app/config/app.php configuration file (add the end):
'Juy\Profiler\Providers\ProfilerServiceProvider',
Add below to the aliases array in app/config/app.php configuration file (add 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 in updates.
php artisan config:publish juy/profiler
Set this option to FALSE to disable the profiler. It is NULL by default and it is dependent debug option on 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
Profiler::disable();
Note:: This will only disable the output, it will still do it's background listening but will not output it to the browser.
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 Laravels 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 colour coded in the Logs part of the profiler - colours may change in future to more accurately reflect the log type.