PHPackages                             nawasara/alerting - 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. nawasara/alerting

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

nawasara/alerting
=================

Central incident bus for Nawasara — register alert rules, dispatch fire/resolve via Alerter facade, state-machine with cooldown + escalation, routes notifications to nawasara/notification channels.

v0.1.0(2d ago)04↑2900%MITPHPPHP ^8.1

Since Jun 9Pushed yesterdayCompare

[ Source](https://github.com/nawasara/alerting)[ Packagist](https://packagist.org/packages/nawasara/alerting)[ RSS](/packages/nawasara-alerting/feed)WikiDiscussions main Synced today

READMEChangelogDependencies (7)Versions (2)Used By (0)

nawasara/alerting
=================

[](#nawasaraalerting)

Central incident bus for Nawasara — register alert rules, dispatch fire/resolve via the `Alerter` facade, state-machine with cooldown + escalation, routes notifications to `nawasara/notification` channels.

Install
-------

[](#install)

```
composer require nawasara/alerting
php artisan migrate
php artisan db:seed --class="Nawasara\Alerting\Database\Seeders\PermissionSeeder"
```

Quick start
-----------

[](#quick-start)

### 1. Register an alert rule in your package's ServiceProvider

[](#1-register-an-alert-rule-in-your-packages-serviceprovider)

```
use Nawasara\Alerting\Facades\Alerter;
use Nawasara\Alerting\Models\AlertRule;

public function boot(): void
{
    Alerter::registerRule(AlertRule::make([
        'key' => 'proxmox.node.disk_critical',
        'severity' => 'critical',
        'category' => 'infrastructure',
        'cooldown_minutes' => 60,
        'description' => 'Node disk usage ≥ 95%',
        'subject_template' => '[CRITICAL] Disk hampir penuh di {context.node}: {context.disk_pct}%',
    ]));
}
```

### 2. Fire the alert from a sync job / listener

[](#2-fire-the-alert-from-a-sync-job--listener)

```
Alerter::fire(
    ruleKey: 'proxmox.node.disk_critical',
    targetType: 'ProxmoxNode',
    targetId: (string) $node->id,
    context: [
        'node' => $node->name,
        'disk_pct' => 96.3,
        'storage' => 'local-lvm',
    ],
);
```

`fire()` is idempotent — calling it again while the alert is already firing does not send a duplicate notification (cooldown gate). Calling again after the cooldown window triggers a re-notify (escalation hint).

### 3. Resolve when the underlying condition clears

[](#3-resolve-when-the-underlying-condition-clears)

```
Alerter::resolve(
    ruleKey: 'proxmox.node.disk_critical',
    targetType: 'ProxmoxNode',
    targetId: (string) $node->id,
);
```

Permissions
-----------

[](#permissions)

- `alerting.view` — view dashboard + states
- `alerting.acknowledge` — acknowledge a firing alert (stop re-notify)
- `alerting.resolve` — manually force a state to ok
- `alerting.silence` — silence a state for N minutes
- `alerting.rule.manage` — code-level rule management (developers)

Sync failure auto-alerting
--------------------------

[](#sync-failure-auto-alerting)

Any package extending `nawasara/sync` `AbstractSyncJob` automatically gets sync-failure alerts when retries are exhausted — no manual rule registration needed. Rule key is `sync.job.failed.{service}`.

State machine
-------------

[](#state-machine)

```
   ┌──────────────────────────────────────────────┐
   │                                              ▼
(none) ──fire──▶ firing ──resolve──▶ ok ──fire──▶ firing
                  │  │
                  │  └─fire (>cooldown)─▶ re-notify (fire_count++)
                  │
                  └─fire (