Laravel APM

Monitor requests/cron/queue execution times in production.

If you have a question: which page to optimize to reduce the server load? Then this package is for you.

Installation

Supported Laravel versions: ^5.5, ^6, ^7, ^8, ^9

composer require mantas-done/laravel-apm

Route :

Default uri = /apm
default name = apm

Daily clear log files by adding scheduled job to App/Console/Kernel.php

$schedule->command('apm:clear')->daily();

Enable APM in .env file

APM=1

Publish config

php artisan vendor:publish --provider="Done\LaravelAPM\ApmServiceProvider" --tag=config  

Why?

Laravel APM can show pages that have the biggest impact on the server load. When you are developing the website, it is hard to tell which pages will receive the most pageviews and which will use the most resources: (per page resource usage) x (pageviews) = (this package stats)

Running this package in production has minimal impact on server load.

Technical

This package logs every user request to a file (storage/app/apm/apm-2020-01-01.txt). On average logging adds an overhead of less than 1 ms to each request (0.001 second).

Recommendations

If you are using Closures for scheduler, it is recommended to add ->setName('some-name');, to be able to distinguish different Closures in APM logs.

$schedule->call(function () {
    DB::table('recent_users')->delete();
})->daily()->setName('some-name'); // add ->setName()

Laravel Telescope

It might seem that they are similar. But Telescope helps figure out what each request does on their own. This package groups all the requests by URL and shows overall statistics.