Skip to main content

Deep Dive

Use the Alert Manager to create, edit, and delete triggers, manage recipients, and review matches (which lines fired and on which channels).
From each match you can also jump to the System Log with the line highlighted and a few lines of context before/after.

First look (no Systems)​

If you haven’t created any System yet, you’ll see an empty state.

When at least one System exists​

Once a System is created, it’s auto-selected in the picker. You can now add recipients and triggers for that System.

Add recipients (required to deliver alerts)​

Define who should receive notifications on each channel you intend to use.

  • SMS / WhatsApp: add valid phone numbers (prefer E.164 format, e.g. +39...).
  • Email: add one email address.
  • Webhook: add an HTTPS endpoint that accepts GET or POST.
Delivery requires AlertFleet

To actually send alerts, connect your AlertFleet API key. Without it, triggers can still match and appear in history, but no notifications are sent.

Create your first trigger​

A trigger fires when its conditions match an incoming log line. You can:

  • Define one main condition plus up to 4 additional conditions (AND/OR).
  • Choose one or more channels (SMS, WhatsApp, Email, Webhook).
  • Set a cooldown (re-notification delay).
    The default is 1 minute to prevent alert storms if a device repeats the same message rapidly.
warning

Notifications are sent only if AlertFleet is integrated and your plan includes the selected channels/credits.

Review triggered lines​

When a trigger fires, you can inspect recent matches:

  • Click the Eye icon on a trigger card to open its match history (last 50 matches).
  • From there, click the icon on the far right to jump to the exact line, highlighted with ±5 lines of context.

Trigger view​

Verify delivery

To confirm that notifications were actually delivered, sign in to AlertFleet and check Alert Logs.

System Log view with highlight​

Tips​

  • Start with narrow conditions and widen them once delivery looks good.
  • Use cooldown to avoid duplicate alerts during noisy incidents.
  • Keep recipients up to date; invalid emails or numbers will prevent delivery.