The examples in this article describe the usage of errors and logs in laravel. Share it with everyone for your reference, the details are as follows:
Logs
The logs in laravel are encapsulated based on monolog. Laravel has done several things on it:
① Simplified functions such as addInfo in monolog into functions like info
② Added two parameters, useFiles and useDailyFiles, making log management and cutting easier
③ If you want to call the monolog method, you need to call the callMonolog function
Okay, let’s see how to implement the following requirements:
Store different log information in different logs
This requirement is very common, such as calling The order log needs to be recorded in order.log, and the record of obtaining store information needs to be recorded in shop.log. You can do this:
<?php use Monolog\Logger; use Monolog\Handler\StreamHandler; use Illuminate\Log\Writer; class BLogger { // 所有的LOG都要求在这里注册 const LOG_ERROR = 'error'; private static $loggers = array(); // 获取一个实例 public static function getLogger($type = self::LOG_ERROR, $day = 30) { if (empty(self::$loggers[$type])) { self::$loggers[$type] = new Writer(new Logger($type)); self::$loggers[$type]->useDailyFiles(storage_path().'/logs/'. $type .'.log', $day); } $log = self::$loggers[$type]; return $log; } }
In this way, different log data will be stored in different log files. Log data information can also be recorded.
Laravel’s error log stack is too long, what should I do?
Use the above Blogger class and record the necessary error information in start/global.php
// 错误日志信息 App::error(function(Exception $exception, $code) { Log::error($exception); $err = [ 'message' => $exception->getMessage(), 'file' => $exception->getFile(), 'line' => $exception->getLine(), 'code' => $exception->getCode(), 'url' => Request::url(), 'input' => Input::all(), ]; BLogger::getLogger(BLogger::LOG_ERROR)->error($err); });
Laravel’s default log does not use segmentation
So laravel’s default logging should be changed to segmentation by default .
Also in start/global.php
Log::useDailyFiles(storage_path().'/logs/laravel.log', 30);
How to record the sql log of a request
This should be further refined. Do you want to record it in real time?
If you don’t want real-time recording, then laravel has DB::getQueryLog to get the sql request obtained by an app request:
## 在filters.php中 App::after(function($request, $response) { // 数据库查询进行日志 $queries = DB::getQueryLog(); if (Config::get('query.log', false)) { BLogger::getLogger('query')->info($queries); } }
If you need real-time recording (that is, you die anywhere time, the sql request of the previous page is also recorded), you need to listen to the illuminate.query event
// 数据库实时请求的日志 if (Config::get('database.log', false)) { Event::listen('illuminate.query', function($query, $bindings, $time, $name) { $data = compact('query','bindings', 'time', 'name'); BLogger::getLogger(BLogger::LOG_QUERY_REAL_TIME)->info($data); }); }
Error
All errors in laravel will all go through the global App::error and then come out
So For example, if you design an interface and want to return json data even if an error occurs, you can do this:
// 错误日志信息 App::error(function(Exception $exception, $code) { // 如果没有路径就直接跳转到登录页面 if ($exception instanceof NotFoundHttpException) { return Redirect::route('login'); } Log::error($exception); $err = [ 'message' => $exception->getMessage(), 'file' => $exception->getFile(), 'line' => $exception->getLine(), 'code' => $exception->getCode(), 'url' => Request::url(), 'input' => Input::all(), ]; BLogger::getLogger(BLogger::LOG_ERROR)->error($err); $response = [ 'status' => 0, 'error' => "服务器内部错误", ]; return Response::json($response); });
If you also want to hold the 404 error:
App::missing(function($exception) { $response = [ 'status' => 0, 'error' => "请求路径错误", ]; return Response::json($response); });
I hope this article will help you. The above will be helpful to everyone in PHP programming based on the Laravel framework.
For more detailed explanations of errors and log usage in laravel, please pay attention to the PHP Chinese website!