Zum Inhalt springen
Produkte

// Benutzung · Monitoring & Alerting

Using system alerts

Some alerts are built in and always on — you don't create them. They live in the System alerts section at the top of Alerts → Rules:

  • Location unreachable — a whole location stopped sending metrics (its agent is down or the site is offline).
  • Resource unreachable — a single resource stopped reporting while its location is still online — for example an iDRAC host that went offline or a node that dropped out. A guest you deliberately powered off keeps reporting its status, so it does not trigger this.

Further system alerts watch backups, certificates, Kubernetes workloads and uptime checks (for example Backup stale); they appear as cards in the same section.

These fire automatically with no configuration. You decide where they go, whether they're active, and, if the default does not fit, how sensitive they are.

Point them at a channel

Out of the box a system alert is tracked (you'll see it in Active) but sends nothing, because it has no channel. Set one up first — see setting up a notification channel — then, in each system-alert card, tick the channel(s) under Notify via. The change saves immediately. The "won't notify" warning disappears once at least one channel is selected.

Turn one off, or silence it briefly

  • Use the on/off button on the card to disable a system alert entirely.
  • Use Mute 1h to silence it for an hour without disabling it (handy during planned maintenance) — see muting an alert.

System alerts can't be deleted — only disabled or muted.

Adjusting sensitivity

The staleness window (how long silence must last before firing) defaults to 90 seconds. It follows the service default unless you set a per-alert value.

Each card shows the values its alert is evaluated from:

  • Location unreachable and Resource unreachable: Stale after (seconds). Empty the box to go back to the service default.
  • The threshold-based system alerts (for example Backup stale): Threshold and For (seconds), how long the condition must hold before the alert fires. An empty For is 0, fire at once.

Type the new value and click Save on the card; only the boxes you changed are sent. A box that does not hold a number is not sent: the page names it. A value the server refuses (for example a window over ~10 years) is shown as an error, and the box keeps what you typed so you can correct it. The name and the query of a system alert cannot be changed.

// Zusammenarbeit

Bereit, Ihre digitale Infrastruktur zu bauen?

Ob individuelle Automatisierung für Ihr Unternehmen oder ein durchgeplantes Netzwerk für Ihr Zuhause — lassen Sie uns über das Projekt sprechen.