Skip to content

Notifications

Eight.ly OS can send notifications when events happen on your server — VMs stopping, backups completing, CPU spiking, disks filling up. Configure notification targets and event rules from the Datacenter Notifications tab.

Where to find it: Infrastructure > Datacenter > Notifications

Notification targets

Email (SMTP)

Send notifications via any SMTP server (Gmail, Mailgun, your own mail server, etc.):

  1. Go to Notifications > Targets
  2. Click Add > Email
  3. Configure SMTP server, port, username, password, sender address
  4. Add recipient email addresses
  5. Send a test notification to verify

Once saved, the SMTP password is write-only: the dashboard shows whether a password is set, never the value itself. Leave the field blank when editing a target to keep the existing password.

Webhooks

Send HTTP POST requests to any URL when events trigger:

  1. Go to Notifications > Targets
  2. Click Add > Webhook
  3. Enter the webhook URL
  4. Optionally configure headers and authentication
  5. Send a test to verify

Works with Discord webhooks, Slack incoming webhooks, ntfy, Gotify, Apprise, Home Assistant, n8n, or any service that accepts HTTP POST.

Event rules

Rules connect events to notification targets. Each rule specifies:

  • Event type — what triggers the notification
  • Target — where to send it
  • Threshold (for resource events) — when to trigger

Available events

Event Fires when
vm.started A VM starts
vm.stopped A VM stops (including crashes)
vm.deleted A VM is deleted
backup.completed A backup job finishes successfully
backup.failed A backup job fails
node.high_cpu CPU usage exceeds threshold
node.high_memory Memory usage exceeds threshold
node.disk_full Disk usage exceeds threshold

Creating a rule

  1. Go to Notifications > Rules
  2. Click Add Rule
  3. Select the event type
  4. Choose the notification target (email, webhook, or both)
  5. For resource events, set the threshold percentage (e.g., 90 for "CPU > 90%")
  6. Save

Notification history

The History sub-tab shows all sent notifications with:

  • Timestamp
  • Event type
  • Target
  • Status (sent / failed)
  • Error message if failed

Use this to verify your notification pipeline is working and to debug delivery issues.

Common setups

Backup monitoring: Create rules for backup.completed and backup.failed pointing to your email. You'll get notified whether backups succeed or fail.

Disk space alerts: Create a node.disk_full rule with a 85% threshold. Get warned before you run out of space.

VM crash alerts: Create a vm.stopped rule to catch unexpected VM shutdowns. Useful for critical VMs running databases or services.