iTranslated by AI

The content below is an AI-generated translation. This is an experimental feature, and may contain errors. View original article
💗

Trying out Laravel Pulse

に公開
Laravel
PHP
tech

What is Laravel Pulse?

Laravel Pulse provides at-a-glance insights into your application's performance and usage. Pulse allows you to track down bottlenecks like slow jobs and endpoints, find your most active users, and more.

Official Site: https://pulse.laravel.com/
Official Documentation: https://laravel.com/docs/10.x/pulse

In short, it makes it easier to find bottlenecks by allowing you to check high-request users, slow requests, and heavy processes via a web interface.

Specifically, I was able to check the following:

  • Request count and job creation count per user
  • Queue progress
  • Cache hit rate check
  • Exception occurrences
  • Slow requests, queries, and jobs

All of these are certainly important items for identifying bottlenecks.
I'm curious, so let's take a quick look.

Installation

I'll install it by following the documentation.

First, I'll modify the composer.json settings so that I can install the beta version package.

"minimum-stability": "beta",
"prefer-stable": true

After that, run the following commands to complete the process.

composer require laravel/pulse
php artisan migrate

It's simple.

Web Interface

By default, the interface can be accessed via /pulse, but this can also be changed in config/pulse.php.

Impressions

The interface is quite clean.
It's also great that you can specify the time period you want to see, such as the last 1 hour, half-day, 1 day, or 1 week. 👍
By the way, this screen uses Livewire and updates the state every few seconds.

Items that can be checked

  • Application Usage: Request count and job creation count per user
  • Queues: Queue progress
  • Cache: Cache hit rate check
  • Exceptions: Exception occurrences
  • Slow Queries: Slow-running queries
  • Slow Jobs: Slow-running jobs
  • Slow Requests: Slow-running requests
  • Slow Outgoing Requests: Slow-running requests (calls made from the server side?)

It seems like it can do a lot more

Although I only took a quick look this time, looking at the article on Laravel News, it seems there are many more things it can do.
Server CPU/memory/storage usage, and customization.

If you are interested, please check out the article.
→ https://laravel-news.com/laravel-pulse

Summary

The contents were simple, but they were all necessary features for finding bottlenecks, so it's great.

If you're interested, please try playing around with it while checking out the Laravel News article or doing some research. ^^

It's simple and seems to have extensibility, so I'd like to introduce it once it's officially released. 😀

Discussion