Weave Code
Weaver
Helps Laravel developers discover, compare, and choose open-source packages. See popularity, security, maintainers, and scores at a glance to make better decisions.
Feedback
Share your thoughts, report bugs, or suggest improvements.
Subject
Message
laravel-pulse-monitoring
laravel-pulse-monitoring
alizharb/agent-skills
claude-code
pulse
monitoring
performance-metrics
custom-recorders
slow-queries
dashboard-auth

Use when configuring, integrating, or parsing application metrics and performance bottlenecks using Laravel Pulse.

Install
php artisan boost:add-skill alizharb/agent-skills

Save this content to: .claude/skills/laravel-pulse-monitoring/SKILL.md

# Laravel Pulse Performance Monitoring

## When To Use

Use this skill when diagnosing slow application routes, resolving database performance issues, tracking cache metrics, or configuring recorders.

## Workflow

1. **Verify configuration**: Verify `config/pulse.php` exists.
2. **Setup slow-query threshold**: Configure limits for slow queries (e.g. queries taking > 500ms).
3. **Register Custom Recorders**: Create and bind custom performance recorders to track application-specific events.
4. **Isolate Dashboard Access**: Ensure only authorized administrators can view the `/pulse` dashboard.

## Examples

### Good Example

```php
// app/Providers/AppServiceProvider.php
namespace App\Providers;

use Illuminate\Support\Facades\Gate;
use App\Models\User;

class AppServiceProvider extends ServiceProvider
{
    public function boot(): void
    {
        // ✅ Restrict dashboard view access securely
        Gate::define('viewPulse', function (User $user) {
            return $user->is_admin;
        });
    }
}
```

### Bad Example

```php
// ❌ Leaving the pulse route open in production without gates or authentication checks.
Route::get('/pulse', function() {
    return view('pulse'); // VULNERABLE!
});
```

Laravel Pulse Performance Monitoring

When To Use

Use this skill when diagnosing slow application routes, resolving database performance issues, tracking cache metrics, or configuring recorders.

Workflow

  1. Verify configuration: Verify config/pulse.php exists.
  2. Setup slow-query threshold: Configure limits for slow queries (e.g. queries taking > 500ms).
  3. Register Custom Recorders: Create and bind custom performance recorders to track application-specific events.
  4. Isolate Dashboard Access: Ensure only authorized administrators can view the /pulse dashboard.

Examples

Good Example

// app/Providers/AppServiceProvider.php
namespace App\Providers;

use Illuminate\Support\Facades\Gate;
use App\Models\User;

class AppServiceProvider extends ServiceProvider
{
    public function boot(): void
    {
        // ✅ Restrict dashboard view access securely
        Gate::define('viewPulse', function (User $user) {
            return $user->is_admin;
        });
    }
}

Bad Example

// ❌ Leaving the pulse route open in production without gates or authentication checks.
Route::get('/pulse', function() {
    return view('pulse'); // VULNERABLE!
});
Weaver

How can I help you explore Laravel packages today?

Conversation history is not saved when not logged in.
Prompt
Add packages to context
No packages found.
jinas/dhivatar
store-doc/laravel-storage-driver
plus-it/laravel-translation-manager
diephp/perhaps
diephp/telegraph
osmaviation/spreadsheet
microsoft/fluentui-system-icons
mmccook/php-json-canonicalization-scheme
middlewares/firewall
qubiqx/montapacking
nyoncode/laravel-package-console
pnscripts/filament-broadquill-lite
pnscripts/laravel-sentfold-lite
vleap/mx-sdk-laravel-internal
twidpay/utils
htetmyathlaing/scout-elasticsearch-driver
artisan-toolbox/front-awesome
ls/client-assistant
users-au/laravel-client
cgv/localized-resource