Laravel Octane
How to monitor a Laravel application served by Octane
By default Inspector register a shutdown function to transfer data from your application to Inspector at the end of each request lifecycle.
Since Octane runs your application in a long running process the shutdown functions will never be called until the Octane server is stopped.
You have to manually flush the data collected by Inspector at end of the HTTP request life cycle.
You can do this by extending the original
WebRequestMonitoring middleware provided by the Inspector package, and overwriting the terminate method to flush the data.Create the new middleware
Use the command below to create the new
InspectorOctaneMiddleware:1
php artisan make:middleware InspectorOctaneMiddleware
Copied!
Flush monitoring data
Overwrite the terminate method to add the flush statement:
1
<?php
2
​
3
namespace App\Http\Middleware;
4
​
5
use Inspector\Laravel\Middleware\WebRequestMonitoring;
6
​
7
class InspectorOctaneMiddleware extends WebRequestMonitoring
8
{
9
/**
10
* Handle tasks after the response has been sent to the browser.
11
*
12
* @param \Illuminate\Http\Request $request
13
* @param \Illuminate\Http\Response $response
14
* @return void
15
*/
16
public function terminate($request, $response)
17
{
18
parent::terminate($request, $response);
19
​
20
inspector()->flush();
21
}
22
}
23
​
Copied!
The terminate method will run after the response has been sent to the browser, and the data will be sent asynchronously in the background.
Registering the middleware
Register the new middleware in
App\Http\Kernel instead of WebRequestMonitoring class:1
/**
2
* The application's route middleware groups.
3
*
4
* @var array
5
*/
6
protected $middlewareGroups = [
7
'web' => [
8
...,
9
//\Inspector\Laravel\Middleware\WebRequestMonitoring::class,
10
\App\Http\Middleware\InspectorFlushMiddleware::class,
11
],
12
13
'api' => [
14
...,
15
//\Inspector\Laravel\Middleware\WebRequestMonitoring::class,
16
\App\Http\Middleware\InspectorFlushMiddleware::class,
17
],
Copied!
Now Inspector is able to recognize the end of a transaction and monitor your application properly.
No configuration is needed for artisan commands and background jobs. They will continue to be monitored as usual.
Last modified 19d ago