Alerting

Loguro supports cooldown-based alerts. When a log matches your conditions, you get notified — once — then the alert enters a cooldown period to prevent spam.

Quick setup

Step 1 — Create a notification channel (account-wide, reusable across projects):

--channels::create

Step 2 — Create an alert (project-specific):

--alerts::create

Send logs that match your conditions and you’ll be notified on the configured channel.

Notification channels

Channels are account-scoped — create them once and use them across any project’s alerts.

Manage channels:

--channels               → list all channels
--channels::create       → add a channel
--channels:<name>        → view or edit
--channels:<name>::delete

Alert conditions

When creating an alert you configure one or more match conditions:

Conditions are ANDed together — all must match for the alert to fire.

Cooldown

The cooldown is the minimum time between notifications for a given alert. Once an alert fires, it silences itself for the cooldown period even if more matching logs arrive.

Set cooldown to match the urgency — a 5-minute cooldown for critical errors, 60 minutes for warnings.

Heartbeat alerts

To be notified when a service stops sending heartbeats:

1. Create an alert with the level watchlist set to heartbeat
2. Set a short cooldown (e.g. 5 minutes)

The alert fires when no heartbeat log arrives within the expected window. Pair this with an Embed Widget to show the status publicly.

Plan limits

When the limit is reached, --alerts::create shows the current count and a link to upgrade.

Managing alerts

--alerts                          → list all alerts
--alerts::create                  → create new alert
--alerts:<name>                   → view or edit
--alerts:<name>::delete           → delete

Notes

• Alerts fire immediately on the first match, then enter cooldown
• Channels are account-wide; alerts are project-specific
• See —channels and —alerts for full command syntax