Laravel错误与日志处理
来源:互联网 发布:藤井莉娜淘宝 编辑:程序博客网 时间:2024/05/18 01:38
App\Exceptions\Handler class is where all exceptions triggered by your application are logged and then rendered back to the user. We'll dive deeper into this class throughout this documentation.
For logging, Laravel utilizes the Monolog library, which provides support for a variety of powerful log handlers. Laravel configures several of these handlers for you, allowing you tochoose between a single log file, rotating log files, or writing error information to the system log.
Error Detail
The debug option in your config/app.php configuration file determines how much information about an error is actually displayed to the user. By default, this option is set to respect the value of the APP_DEBUG environment variable, which is stored in your .env file.
For local development, you should set the APP_DEBUG environment variable to true. In your production environment,this value should always be false. If the value is set to true in production, you risk exposing sensitive configuration values to your application's end users.
Laravel supports writing log information to single files, daily files, the syslog, and the errorlog. To configure which storage mechanism Laravel uses, you should modify the logoption in your config/app.php configuration file. For example, if you wish to use daily log files instead of a single file, you should set the log value in your app configuration file to daily:
'log'=>'daily'
Maximum Daily Log Files
When using the daily log mode, Laravel will only retain five days of log files by default. If you want to adjust the number of retained files, you may add a log_max_files configuration value to yourapp configuration file:
'log_max_files'=>30
Severity Levels
When using Monolog, log messages may have different levels of severity. By default, Laravel writes all log levels to storage. However, in your production environment, you may wish to configure the minimum severity that should be logged by adding the log_level option to your app.phpconfiguration file.
Once this option has been configured, Laravel will log all levelsgreater than or equal tothe specified severity. For example, a default log_level of error will log error, critical, alert, and emergencymessages:
'log_level'=>env('APP_LOG_LEVEL','error'),
Monolog recognizes the following severity levels -from least severe to most severe:debug, info, notice, warning, error, critical, alert, emergency.
Exception Handler
All exceptions are handled by the App\Exceptions\Handler class. This class contains two methods:report and render. We'll examine each of these methods in detail. The report method is used to log exceptions or send them to an external service like Bugsnag or Sentry. By default, the reportmethod simply passes the exception to the base class where the exception is logged. However, you are free to log exceptions however you wish.
Ignoring Exceptions By Type想要忽略的
The $dontReport propertyof the exception handler contains an array of exception types that will not be logged.
HTTP Exceptions
Some exceptions describe HTTP error codes from the server. For example, this may be a "page not found" error (404), an "unauthorized error" (401) or even a developer generated 500 error. In order to generate such a response from anywhere in your application, you may use the abort helper:
abort(404);
abort(403,'Unauthorized action.');
Custom HTTP Error Pages
For example, if you wish to customize the error page for 404 HTTP status codes, create aresources/views/errors/404.blade.php
The views within this directory should be named to match the HTTP status code they correspond to. The HttpException instance raised by the abort function will be passed to the view as an $exception variable.
Logging
emergency, alert, critical, error,warning, notice, info and debug.
By default, Laravel is configured to create a log file for your application in the storage/logs directory. You may write information to the logs using the Log facade:
Log::emergency($message);Log::alert($message);Log::critical($message);Log::error($message);Log::warning($message);Log::notice($message);Log::info($message);Log::debug($message);
Contextual Information上下文信息
An array of contextual data
https://laravel.com/docs/5.3/errors
0 0
- Laravel错误与日志处理
- laravel中的错误与日志
- laravel(九) laravel 的错误与日志
- laravel自定义错误页和错误日志处理
- laravel中的错误与日志(可以自定义日志目录和log文件名)
- laravel中的错误与日志(可以自定义日志目录和log文件名)
- laravel 学习笔记三 :错误&日志
- ubuntu 错误处理日志
- android自定义异常处理与错误日志上传
- Laravel 日志
- Web系统错误日志处理
- php日志错误异常处理
- logstash 处理nginx 错误日志
- [李景山php]每天laravel[037]-laravel 系统服务 --- 错误及日志
- php 中用户触发错误与记录错误日志及异常处理
- PDO错误与错误处理
- 异常处理与错误处理
- 异常与错误处理
- Android Data Binding 系列(一) -- 详细介绍与使用
- Unity 3D - 光照计算中的diffuse的计算公式
- 圆形倒计时
- Skype和QQ语音有几个区别
- C语言笔记2--控制流
- Laravel错误与日志处理
- PHP Mysql 用PHP查看mysql数据库所有表名
- TCP/IP详解,卷1:协议,第二章链路层
- Letcode 1.Two Sum
- 项目组J2ee程序员的标志,你中招没 转载+评论
- 【附】Cookie和Session的清除,实现网站的退出功能
- Why writing files from the kernel is bad ?
- java三大特性之多态
- Linux rpm 命令参数使用详解[介绍和应用]