Skip to main content

The diagnostic command

The command exits with an error (code 1) as soon as one check fails; warnings do not change the code. Wire it into your monitoring:
The same thing is visible in Settings → Maintenance.

HTTP probes

/up checks neither Horizon nor the cron line: pair it with lekalao:diagnose.

Horizon

/horizon (platform administrators) shows the queues live, the throughput, the slow jobs and the failed ones. A failed job is retried from there, or with:

Logs

Laravel writes to storage/logs/laravel.log. In production:
.env
Worth watching in particular: rendering errors (MJML, templates), refusals from providers, and errors from the SMTP relay.

What warns the teams

Lekalao tells the teams about what concerns them, with nothing for the administrator to do:
  • a campaign paused by sending safety;
  • the summary of a campaign after it went out;
  • the weekly summary of every list that asks for one.
A domain whose DNS is no longer right, or a webhook endpoint switched off, show up in the interface, without an e-mail.