Alerts
The Alerts view (5) is a thin front-end over /api/projects/[id]/alerts. The same alerts you see here show up on the web console.
| Key | Action |
|---|---|
↑/↓ or j/k | Move cursor |
c | Create alert (wizard) |
space | Toggle active / paused for the selected alert |
d | Delete alert |
r | Reload |
Each row shows: active dot (green ●) or paused (○), name, target channel (with type), and the matched levels — color-coded.
Create from scratch — c
The wizard walks five steps. Every step has its own modal; press esc at any step to cancel.
- Name — short label, used in notifications. Free text, required.
- Channel — single-select from your active notification channels. If you have none, the wizard shows a hint to run
loguro channels create …and bails — alerts need a delivery target. - Levels — multi-select with
space. Leave empty to match every level. The six options are described in Search & filtering. - Message contains — optional substring filter on the log message. Empty = match any message.
- Cooldown — single-select from preset windows: backend default, 5m, 15m, 30m, 1h, 2h, 6h, 12h, 24h. The cooldown is the minimum time between notifications once the alert fires.
POST to /api/projects/[id]/alerts, list reloads, status bar shows ✓ alert "<name>" created.
Create from a log — a
Open the log in detail (Logs → enter), then press a. The wizard opens with three fields pre-filled from the log:
| Field | Value |
|---|---|
| Name | <LEVEL>: <first 40 chars of message> |
| Levels | [log.level] — single-element list |
| Message contains | First 80 chars of the log message |
Walk through the remaining steps (channel, optionally edit message, cooldown) and submit. You stay in the log detail view; status bar confirms.
This is the fastest path from “I just saw an error I never want to miss again” to a working alert — three keypresses if you accept the pre-fill (a → channel pick → enter through the rest).
Toggle without leaving the list
space flips isActive. The backend PUT requires the full alert payload, so the TUI re-sends every field with only isActive flipped — no merge bugs.
Heartbeat alerts
To be notified when a service stops sending heartbeats, create an alert with levels = heartbeat and a short cooldown (5–15m). See Alerting on the docs site for the full pattern.
Limits
Free plan is capped at 1 alert per project, Solo at 5, Pro and Scale are unlimited. The Alerts view header shows N/<limit> alerts so you know where you are.