DI and actions

There are three equivalent entry points, and they all run the same code. Pick the one that fits the call site:

• The Health facade — the shortest, and the recommended default.
• The manager, RoundlyConsulting\Alerts\HealthManager — the facade’s root, a container singleton. Inject it through the constructor for the same API as an explicit dependency, with no static calls.
• The actions in RoundlyConsulting\Alerts\Actions — single-purpose classes with an execute() method, for composing into your own actions, jobs and commands.

Injecting the manager

use RoundlyConsulting\Alerts\HealthManager;

final class MaintenanceController
{
    public function __construct(private HealthManager $health) {}

    public function __invoke(Team $team): void
    {
        $this->health->silences()->mute('*', until: now()->addHour(), for: $team);
        $this->health->for($team)->run(DiskUsageCheck::class);
    }
}

Health::fake() swaps the manager for the facade and for anything that injects HealthManager, so constructor-injected code is faked too.

Calling an action

use RoundlyConsulting\Alerts\Actions\MuteAlertsAction;
use RoundlyConsulting\Alerts\Actions\ScheduleHealthCheckAction;
use RoundlyConsulting\Alerts\DataTransferObjects\ScheduleHealthCheckData;

app(ScheduleHealthCheckAction::class)->execute($team, new ScheduleHealthCheckData(check: DiskUsageCheck::class));
app(MuteAlertsAction::class)->execute('disk_usage_check', until: now()->addHour());

ScheduleHealthCheckAction takes the owner and a ScheduleHealthCheckData DTO (see Scheduling checks).

Facade method → action

RunHealthCheckAction is internal: it is the pipeline behind the queued HealthCheckJob and RunHealthCheckNowAction. To run a scheduled row yourself — in a custom job, for example — call Health::for($row->notifiable)->run($row).