PHPackages                             axelvds/laravel-uptime-monitor-extended - PHPackages - PHPackages  [Skip to content](#main-content)[PHPackages](/)[Directory](/)[Categories](/categories)[Trending](/trending)[Leaderboard](/leaderboard)[Changelog](/changelog)[Analyze](/analyze)[Collections](/collections)[Log in](/login)[Sign up](/register)

1. [Directory](/)
2. /
3. [Logging & Monitoring](/categories/logging)
4. /
5. axelvds/laravel-uptime-monitor-extended

ActiveLibrary[Logging & Monitoring](/categories/logging)

axelvds/laravel-uptime-monitor-extended
=======================================

Extended uptime monitoring package for Laravel with IP/ping support, per-monitor frequency, active toggle, and dashboard widgets

v1.1.10(7mo ago)01931[1 issues](https://github.com/AxelvdS/laravel-uptime-monitor-extended/issues)MITPHPPHP ^8.1

Since Nov 8Pushed 3mo agoCompare

[ Source](https://github.com/AxelvdS/laravel-uptime-monitor-extended)[ Packagist](https://packagist.org/packages/axelvds/laravel-uptime-monitor-extended)[ RSS](/packages/axelvds-laravel-uptime-monitor-extended/feed)WikiDiscussions main Synced today

READMEChangelogDependencies (6)Versions (41)Used By (0)

Laravel Uptime Monitor Extended
===============================

[](#laravel-uptime-monitor-extended)

[![Status](https://camo.githubusercontent.com/63984326d5f296718e624453f4cfd50921318a98a9ab02b3ca365e9194b5d340/68747470733a2f2f696d672e736869656c64732e696f2f62616467652f7374617475732d737461626c652d677265656e)](https://camo.githubusercontent.com/63984326d5f296718e624453f4cfd50921318a98a9ab02b3ca365e9194b5d340/68747470733a2f2f696d672e736869656c64732e696f2f62616467652f7374617475732d737461626c652d677265656e)[![Version](https://camo.githubusercontent.com/15856784c4bef6f07c960eb6fc645aea2a0b4eb5968939b5b65e5cc1fe961acc/68747470733a2f2f696d672e736869656c64732e696f2f62616467652f76657273696f6e2d312e312e31302d626c7565)](https://camo.githubusercontent.com/15856784c4bef6f07c960eb6fc645aea2a0b4eb5968939b5b65e5cc1fe961acc/68747470733a2f2f696d672e736869656c64732e696f2f62616467652f76657273696f6e2d312e312e31302d626c7565)

An extended uptime monitoring package for Laravel that builds upon [Spatie's Laravel Uptime Monitor](https://github.com/spatie/laravel-uptime-monitor) with additional features including IP/ping monitoring, per-monitor frequency settings, active/inactive toggles, and built-in dashboard widgets.

**Architecture**: The core monitoring functionality is available for any Laravel project. If you're using [Laravel Filament](https://filamentphp.com), you can optionally enable Filament resources and widgets for a complete admin panel experience.

Features
--------

[](#features)

### Core Features (Available in All Laravel Projects)

[](#core-features-available-in-all-laravel-projects)

- ✅ **IP Address Monitoring** - Monitor devices and servers via ping (ICMP)
- ✅ **URL Monitoring** - Monitor websites and APIs via HTTP/HTTPS (uses Spatie's functionality)
- ✅ **SSL Certificate Monitoring** - Automatic SSL certificate expiration checks
- ✅ **Per-Monitor Frequency** - Set different check intervals for each monitor
- ✅ **Active/Inactive Toggle** - Enable or disable monitoring per device/service
- ✅ **Response Checking** - Verify specific content in responses (login pages, API responses, etc.)
- ✅ **Configurable Log Retention** - Set how long to keep monitoring logs
- ✅ **Artisan Commands** - CLI commands for checking monitors and cleaning up logs

### Filament Integration (Optional)

[](#filament-integration-optional)

If you're using Laravel Filament, you also get:

- ✅ **Monitor Resource** - Full CRUD interface for managing monitors
- ✅ **Dashboard Widgets** - Built-in Filament widgets for monitoring statistics
    - Devices up/down/SSL issues statistics widget
    - Table of devices currently down widget
    - Uptime graph widget showing trends over time
- ✅ **Native Filament Experience** - All features work seamlessly within your Filament admin panel

Requirements
------------

[](#requirements)

- PHP 8.1 or higher (PHP 8.3+ recommended)
- Laravel 10.0 or higher
- [Spatie Laravel Uptime Monitor](https://github.com/spatie/laravel-uptime-monitor) (v4.0+) - **Automatically installed as a dependency**

**Optional (for Filament integration):**

- [Laravel Filament](https://filamentphp.com) (v3.0+ or v4.0+)

Installation
------------

[](#installation)

1. Install the package via Composer:

```
composer require axelvds/laravel-uptime-monitor-extended
```

> **Note**: Spatie's Laravel Uptime Monitor is automatically installed as a dependency. You don't need to install it separately.

2. Publish Spatie's migrations:

```
php artisan vendor:publish --provider="Spatie\UptimeMonitor\UptimeMonitorServiceProvider"
```

3. Publish this package's configuration and migrations:

```
php artisan vendor:publish --provider="AxelvdS\UptimeMonitorExtended\UptimeMonitorExtendedServiceProvider"
```

This will publish:

- Configuration file: `config/uptime-monitor-extended.php`
- Migrations: `database/migrations/` (extends monitors table and creates monitors\_logs table)

4. Run the migrations:

```
php artisan migrate
```

This will automatically run migrations in the correct order:

1. **Spatie's migrations** - Creates the `monitors` table
2. **This package's migrations** - Extends the `monitors` table and creates the `monitors_logs` table

> **Note**: The migrations are timestamped to ensure they run in the correct order automatically. If you get an error about the `monitors` table not existing, make sure you've published Spatie's migrations first (step 2).

### Filament Integration (Optional)

[](#filament-integration-optional-1)

If you're using Laravel Filament and want to use the Filament resources and widgets:

1. Install Filament (if not already installed):

```
composer require filament/filament:"^3.0|^4.0"
```

2. Register the resources and widgets in your Filament panel provider (typically `app/Providers/Filament/AdminPanelProvider.php`) and make sure they are not already there:

```
use AxelvdS\UptimeMonitorExtended\Filament\UptimeMonitorExtendedFilamentServiceProvider;

public function panel(Panel $panel): Panel
{
    return $panel
        // ... your other panel configuration
        ->discoverResources(in: app_path('Filament/Resources'), for: 'App\\Filament\\Resources')
        ->discoverWidgets(in: app_path('Filament/Widgets'), for: 'App\\Filament\\Widgets')
        ->resources([
            // ... your other resources
        ])
        ->widgets([
            // ... your other widgets
        ]);
}

protected function boot(): void
{
    parent::boot();

    // Register uptime monitor resources and widgets
    UptimeMonitorExtendedFilamentServiceProvider::registerForPanel(
        $this->panel(static::new())
    );
}
```

Alternatively, you can register them directly in your panel method:

```
use AxelvdS\UptimeMonitorExtended\Filament\Resources\MonitorResource;
use AxelvdS\UptimeMonitorExtended\Filament\Widgets\DevicesDownTableWidget;
use AxelvdS\UptimeMonitorExtended\Filament\Widgets\UpDownStatsWidget;
use AxelvdS\UptimeMonitorExtended\Filament\Widgets\UptimeGraphWidget;

public function panel(Panel $panel): Panel
{
    return $panel
        ->resources([
            MonitorResource::class,
            // ... your other resources
        ])
        ->widgets([
            UpDownStatsWidget::class,
            DevicesDownTableWidget::class,
            UptimeGraphWidget::class,
            // ... your other widgets
        ]);
}
```

Configuration
-------------

[](#configuration)

After publishing the configuration file, you can customize the settings in `config/uptime-monitor-extended.php`:

```
return [
    // Route prefix for dashboard
    'route_prefix' => env('UPTIME_MONITOR_ROUTE_PREFIX', 'uptime-monitor'),

    // Log retention in days (null = unlimited)
    'log_retention_days' => env('UPTIME_MONITOR_LOG_RETENTION_DAYS', 30),

    // Default check frequency in minutes
    'default_frequency_minutes' => env('UPTIME_MONITOR_DEFAULT_FREQUENCY', 5),

    // Ping configuration
    'ping' => [
        'timeout' => env('UPTIME_MONITOR_PING_TIMEOUT', 3),
        'count' => env('UPTIME_MONITOR_PING_COUNT', 1),
        'interval' => env('UPTIME_MONITOR_PING_INTERVAL', 0.2),
    ],

    // Filament configuration (optional)
    'filament' => [
        // Navigation label for the Monitor resource
        'navigation_label' => env('UPTIME_MONITOR_NAVIGATION_LABEL', 'Monitors'),

        // Optional: Navigation group (set to null or don't set to have no group)
        'navigation_group' => env('UPTIME_MONITOR_NAVIGATION_GROUP') ?: null,
    ],

    // Auto-schedule commands (default: true)
    'auto_schedule' => env('UPTIME_MONITOR_AUTO_SCHEDULE', true),

    // Dashboard configuration
    'dashboard' => [
        'enabled' => env('UPTIME_MONITOR_DASHBOARD_ENABLED', true),
        'graph_data_points' => env('UPTIME_MONITOR_GRAPH_DATA_POINTS', 24),
        'refresh_interval' => env('UPTIME_MONITOR_DASHBOARD_REFRESH', 60),
        'graph_height' => env('UPTIME_MONITOR_GRAPH_HEIGHT', 200), // pixels
    ],
];
```

Usage
-----

[](#usage)

### Creating Monitors

[](#creating-monitors)

#### HTTP/HTTPS Monitor

[](#httphttps-monitor)

```
use Spatie\UptimeMonitor\Models\Monitor;

// Create an HTTPS monitor
Monitor::create([
    'url' => 'https://example.com',
    'monitor_type' => 'https',
    'frequency_minutes' => 5,
    'is_active' => true,
    'look_for_string' => 'Welcome', // Optional: check for specific content
]);

// Create an HTTP monitor for an IP address
Monitor::create([
    'url' => 'http://192.168.1.100:8080',
    'monitor_type' => 'http',
    'frequency_minutes' => 1,
    'is_active' => true,
]);
```

#### Ping Monitor

[](#ping-monitor)

```
use Spatie\UptimeMonitor\Models\Monitor;

// Create a ping monitor for a server/device
Monitor::create([
    'url' => '192.168.1.1', // IP address
    'monitor_type' => 'ping',
    'frequency_minutes' => 1,
    'is_active' => true,
    'notes' => 'Main router',
]);
```

### Checking Monitors

[](#checking-monitors)

Run the extended check command:

```
# Check all active monitors
php artisan uptime-monitor:check-extended

# Check a specific monitor
php artisan uptime-monitor:check-extended --monitor-id=1
```

### Scheduling Checks

[](#scheduling-checks)

**Automatic Scheduling (Default)**

By default, the package automatically registers scheduled commands. No manual configuration is required! The commands are scheduled to run:

- Monitor checks: Every minute
- Log cleanup: Daily

> **Note**: Automatic scheduling may not be visible in your `routes/console.php` file, but the commands are still registered and will run. If you prefer to see and control the scheduling explicitly, use manual scheduling below.

**Manual Scheduling (Optional)**

If you prefer to manually control scheduling or want to see the scheduled commands explicitly in your `routes/console.php` file, you can disable auto-scheduling by setting in your `.env`:

```
UPTIME_MONITOR_AUTO_SCHEDULE=false
```

Then add to your `routes/console.php` (Laravel 11+):

```
use Illuminate\Support\Facades\Schedule;

Schedule::command('uptime-monitor:check-extended')
    ->everyMinute()
    ->withoutOverlapping()
    ->runInBackground();

Schedule::command('uptime-monitor:cleanup-logs')
    ->daily()
    ->withoutOverlapping();
```

Or for Laravel 10, add to your `app/Console/Kernel.php`:

```
protected function schedule(Schedule $schedule)
{
    // Check monitors every minute
    $schedule->command('uptime-monitor:check-extended')
        ->everyMinute()
        ->withoutOverlapping()
        ->runInBackground();

    // Clean up old logs daily
    $schedule->command('uptime-monitor:cleanup-logs')
        ->daily()
        ->withoutOverlapping();
}
```

**Important:** Make sure your Laravel scheduler is running. Add this to your crontab:

```
* * * * * cd /path-to-your-project && php artisan schedule:run >> /dev/null 2>&1
```

### Dashboard

[](#dashboard)

#### Filament Dashboard (Recommended)

[](#filament-dashboard-recommended)

If you're using Filament, the package automatically provides:

- **Monitor Resource** - Full CRUD interface for managing monitors
- **Up/Down Stats Widget** - Statistics showing devices up/down/SSL issues
- **Devices Down Table Widget** - Table of monitors currently down
- **Uptime Graph Widget** - Visual graph showing uptime trends over time

These will appear in your Filament admin panel automatically once registered.

#### Legacy Dashboard (Non-Filament Projects)

[](#legacy-dashboard-non-filament-projects)

For projects without Filament, a simple Blade-based dashboard is available:

Access the dashboard at: `http://your-app.com/uptime-monitor`

The dashboard provides:

- Real-time statistics (devices up/down/SSL issues)
- Uptime graph over time
- Table of devices currently down

**Note**: The legacy dashboard is automatically disabled if Filament is detected. To enable it manually, set `dashboard.enabled` to `true` in your config file.

### API Endpoints

[](#api-endpoints)

The package provides API endpoints for dashboard data (only available when using the legacy dashboard):

- `GET /uptime-monitor/api/up-down-stats` - Get up/down statistics
- `GET /uptime-monitor/api/devices-down?limit=10` - Get list of devices down
- `GET /uptime-monitor/api/uptime-graph?hours=24&interval=60` - Get graph data

### Managing Monitors

[](#managing-monitors)

```
use Spatie\UptimeMonitor\Models\Monitor;

// Toggle active status
$monitor = Monitor::find(1);
$monitor->is_active = false;
$monitor->save();

// Update frequency
$monitor->frequency_minutes = 10;
$monitor->save();

// Get monitor logs
use AxelvdS\UptimeMonitorExtended\Models\MonitorLog;

$logs = MonitorLog::where('monitor_id', 1)
    ->orderBy('checked_at', 'desc')
    ->get();
```

Monitor Types
-------------

[](#monitor-types)

- **`https`** - HTTPS monitoring with SSL certificate checks
- **`http`** - HTTP monitoring (no SSL checks)
- **`ping`** - ICMP ping monitoring for IP addresses
- **`tcp`** - TCP port monitoring (e.g., `192.168.1.1:22` or `example.com:3306`)

Response Checking
-----------------

[](#response-checking)

For HTTP/HTTPS monitors, you can check for specific content in responses using the `look_for_string` field:

```
Monitor::create([
    'url' => 'https://api.example.com/health',
    'monitor_type' => 'https',
    'look_for_string' => '{"status":"ok"}', // Check for this string in the response body
    'frequency_minutes' => 5,
]);
```

**How it works:**

- If `look_for_string` is set, after a successful HTTP response (status 200-399), the package checks if the string exists in the response body
- If the string is **not found**, the monitor is marked as `down` with the error message: "Required string '...' not found in response"
- If the string **is found**, the monitor remains `up`
- This is useful for verifying that login pages, API responses, or specific content is present on the page

**Example use cases:**

- Verify a login page contains "Welcome" or "Dashboard"
- Check that an API endpoint returns a specific JSON key
- Ensure a maintenance page doesn't appear (check for absence of "Maintenance Mode")

Log Retention
-------------

[](#log-retention)

Configure log retention in the config file or via environment variable:

```
UPTIME_MONITOR_LOG_RETENTION_DAYS=30
```

Set to `null` to keep logs indefinitely.

Platform Compatibility
----------------------

[](#platform-compatibility)

### Ping Monitoring

[](#ping-monitoring)

Ping monitoring works on:

- ✅ Linux
- ✅ macOS
- ✅ Windows

Note: Some shared hosting environments may restrict ping functionality. In such cases, use HTTP monitoring instead.

Events
------

[](#events)

This package extends Spatie's events. You can listen to:

- `Spatie\UptimeMonitor\Events\UptimeCheckFailed`
- `Spatie\UptimeMonitor\Events\UptimeCheckRecovered`
- `Spatie\UptimeMonitor\Events\UptimeCheckSucceeded`

Database Schema
---------------

[](#database-schema)

The package extends Spatie's `monitors` table with:

- `monitor_type` - Type of monitor (http, https, ping)
- `frequency_minutes` - Check frequency in minutes (per monitor)
- `is_active` - Active/inactive toggle
- `last_check_at` - Timestamp of last check
- `ping_timeout` - Ping timeout (for ping monitors)
- `notes` - Optional notes/description

It also creates a `monitors_logs` table for storing check history.

Troubleshooting
---------------

[](#troubleshooting)

### Ping not working

[](#ping-not-working)

- Ensure your server has permission to execute ping commands
- Check if ping is available: `which ping` (Linux/Mac) or `where ping` (Windows)
- Some shared hosting may restrict ping - use HTTP monitoring instead

### Monitors not checking

[](#monitors-not-checking)

- Ensure monitors are marked as `is_active = true`
- Check that the scheduled command is running
- Verify `frequency_minutes` is set correctly
- Check `last_check_at` to see when monitors were last checked

Contributing
------------

[](#contributing)

Contributions are welcome! Please feel free to submit a Pull Request.

License
-------

[](#license)

This package is open-sourced software licensed under the [MIT license](LICENSE.md).

Credits
-------

[](#credits)

This package extends [Spatie's Laravel Uptime Monitor](https://github.com/spatie/laravel-uptime-monitor) package.

Support
-------

[](#support)

For issues and questions, please open an issue on GitHub.

###  Health Score

40

—

FairBetter than 86% of packages

Maintenance71

Regular maintenance activity

Popularity14

Limited adoption so far

Community7

Small or concentrated contributor base

Maturity56

Maturing project, gaining track record

 Bus Factor1

Top contributor holds 100% of commits — single point of failure

How is this calculated?**Maintenance (25%)** — Last commit recency, latest release date, and issue-to-star ratio. Uses a 2-year decay window.

**Popularity (30%)** — Total and monthly downloads, GitHub stars, and forks. Logarithmic scaling prevents top-heavy scores.

**Community (15%)** — Contributors, dependents, forks, watchers, and maintainers. Measures real ecosystem engagement.

**Maturity (30%)** — Project age, version count, PHP version support, and release stability.

###  Release Activity

Cadence

Every ~0 days

Total

40

Last Release

234d ago

Major Versions

v0.1.41 → v1.0.02025-11-09

### Community

Maintainers

![](https://www.gravatar.com/avatar/3df78bb920e071f71d51784e0ad0a8c665febab9ae7d6e22a4fdbef4fb5c72c4?d=identicon)[AxelvdS](/maintainers/AxelvdS)

---

Top Contributors

[![AxelvdS](https://avatars.githubusercontent.com/u/144521959?v=4)](https://github.com/AxelvdS "AxelvdS (72 commits)")

---

Tags

health-checklaravellaravel-packagemonitoringphppingssl-certificateunder-developmentuptimeuptime-monitorwork-in-progresslaravelmonitoringssldashboardwidgetspinguptime

###  Code Quality

TestsPHPUnit

### Embed Badge

![Health badge](/badges/axelvds-laravel-uptime-monitor-extended/health.svg)

```
[![Health](https://phpackages.com/badges/axelvds-laravel-uptime-monitor-extended/health.svg)](https://phpackages.com/packages/axelvds-laravel-uptime-monitor-extended)
```

###  Alternatives

[laravel/ai

The official AI SDK for Laravel.

1.0k3.2M194](/packages/laravel-ai)[spatie/laravel-health

Monitor the health of a Laravel application

87512.0M165](/packages/spatie-laravel-health)[psalm/plugin-laravel

Psalm plugin for Laravel

3355.3M346](/packages/psalm-plugin-laravel)[illuminate/queue

The Illuminate Queue package.

21332.6M1.6k](/packages/illuminate-queue)[mike-bronner/laravel-model-caching

Automatic caching for Eloquent models.

2.4k91.9k1](/packages/mike-bronner-laravel-model-caching)

PHPackages © 2026

[Directory](/)[Categories](/categories)[Trending](/trending)[Changelog](/changelog)[Analyze](/analyze)