Errors & Logging
All of the configuration options regarding errors and logging live in the application/config/errors.php file. Let's jump right in.
The ignore option contains an array of error levels that should be ignored by Laravel. By "ignored", we mean that we won't stop execution of the script on these errors. However, they will be logged when logging is enabled.
The detail option indicates if the framework should display the error message and stack trace when an error occurs. For development, you will want this to be true. However, in a production environment, set this to false. When disabled, the view located in application/views/error/500.php will be displayed, which contains a generic error message.
To enable logging, set the log option in the error configuration to "true". When enabled, the Closure defined by the logger configuration item will be executed when an error occurs. This gives you total flexibility in how the error should be logged. You can even e-mail the errors to your development team!
By default, logs are stored in the storage/logs directory, and a new log file is created for each day. This keeps your log files from getting crowded with too many messages.
The Logger Class
Sometimes you may wish to use Laravel's Log class for debugging, or just to log informational messages. Here's how to use it:
Writing a message to the logs:
Log::write('info', 'This is just an informational message!');
Using magic methods to specify the log message type:
Log::info('This is just an informational message!');