Zum Inhalt springen
Produkte

// Benutzung · Monitoring & Alerting

Setting up a notification channel

A notification channel is where alerts are delivered. Set one up before (or while) creating alert rules — a rule with no channel fires silently.

  1. Open Alerts → the Channels tab.
  2. In New channel:
    • Name — a label you'll recognise (e.g. ops-ntfy, oncall-email).
    • Kind — one of ntfy, discord, matrix, email.
    • Config — the fields change with the kind:
      • ntfy — server (default https://ntfy.sh), topic, and an optional access token for protected topics.
      • discord — the incoming webhook URL for the target channel.
      • matrix — homeserver, room id (!room:server), and an access token.
      • email — SMTP host/port, username, password, from, and to addresses.
  3. Select Create channel.

Channel secrets are encrypted at rest and never shown back — to change a secret, re-enter it and save.

A channel can send to any LAN or public host, but not to the hub itself: a destination on loopback (localhost, 127.0.0.1) or one of the hub's own services (VictoriaMetrics, NATS, SurrealDB, inventory-svc, ingestion-svc) is refused when you save, with the reason. Point it at the host's LAN address or name instead. Webhooks must not redirect: use the final URL. See Alerting → Where a channel may deliver.

Testing a channel

On a channel's row, select Test. Fleeger sends a real test notification through it and reports success or the exact error, so you can confirm the config before wiring it to a rule.

Editing / deleting

  • Edit re-opens the form (the kind can't change; create a new channel for a different kind). Re-enter the config to replace the stored secret.
  • Delete removes the channel. Rules that referenced it simply stop using it.

Creating, editing and deleting a channel is recorded in the audit log: who did it and which config fields changed, never their values (the webhook URL, token or password). While the audit log cannot record it (inventory-svc down or not yet upgraded) the change is refused with 503 and nothing is changed; try again once inventory-svc is back.

// 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.