Mastering Proxmox VE Notification Framework: Get Telegram & Email Alerts in a Flash

Alerting Systems – The “Eyes and Ears” of a Proxmox Admin

It’s 2 AM, and a hard drive in your 4-bay ZFS cluster suddenly dies, or your company’s most critical 500GB backup fails due to disk space. If you wait until tomorrow morning to see the bright red text on the Dashboard, you might have already missed the golden window to save your data.

Before version 8.1, configuring notifications on Proxmox VE was quite a hassle. You often had to dive deep into Postfix or write time-consuming manual scripts. With the new Notification Framework, Proxmox has made this process much more professional and intuitive.

In the 12-VM homelab I run, Telegram was the first alert channel I set up. It helps me handle incidents even when I’m at a coffee shop or on the move.

Quick Start: Get Email Alerts in 5 Minutes

If you only need to receive notifications via the default Email (usually via local postfix), follow these quick steps:

1. Access the Proxmox Web GUI.
2. Go to Datacenter > Notifications.
3. In the Targets tab, find the default target named mail-to-root.
4. Click Edit and enter your email address in the Recipient Address field.
5. Click Test to verify. If SMTP is ready on the host, the email will land straight in your inbox.

However, this method still depends on Postfix in the underlying OS. For more flexibility, we should use a direct SMTP Target or Telegram, especially if you already use a Proxmox Mail Gateway for your infrastructure.

How It Works: Targets and Matchers

The secret to mastering this system lies in two concepts:

• Targets: Destinations for messages (Email, Telegram, Gotify, Webhook).
• Matchers: Rules that decide when to send and what to send. You can filter to only receive Error reports and stay silent on successful backups.

Setting Up a Telegram Target – Get Instant Messages

Telegram is my preferred channel due to its extremely fast push speed and the fact that it’s completely free.

Step 1: Create a Telegram Bot

Open Telegram, find @BotFather, and type /newbot. Save the provided API Token. Then, chat with @userinfobot to get your personal Chat ID or a technical group ID.

Step 2: Configure on Proxmox

Go back to Datacenter > Notifications > Targets. Click Add > Telegram and fill in the details:

• Name: Telegram-Alerts
• Token: Paste the API Token from BotFather.
• Chat ID: Paste the ID from userinfobot.
• Author: Proxmox-Node-01 (Name to distinguish if you have multiple servers).

Click Test. If your phone buzzes with a test notification, you’re 90% there.

Configuring Matchers: Don’t Let Notifications Annoy You

Don’t turn Telegram into a message dump. If it alerts you every time a VM starts or a backup finishes, you’ll soon start missing critical errors because you’ve developed a habit of ignoring notifications.

1. Switch to the Matchers tab and click Add.
2. Name it Critical-Only and select Telegram-Alerts as the Target.
3. Under Match Severity, select Error and Warning.
4. Skip the Info level so your phone doesn’t buzz pointlessly every night.

Now, the system will only “knock on your door” when there is an actual issue that needs your attention.

Pro Tips for SysAdmins

1. “Defense in Depth” Strategy

Never rely on a single channel. If the datacenter network goes down, Telegram will be paralyzed. Configure a backup SMTP target via Gmail or SendGrid.

2. Clear Cluster Identification

When managing 3 or more clusters, name your Targets with the location (e.g., Telegram-HCM-Core). This helps you locate the issue in less than a second just by looking at your lock screen, even across a Site-to-Site VPN.

3. Monitor ZFS Scrub Status

A handy tip is to configure a Matcher to catch ZFS events. When the Scrub feature detects checksum errors on a drive, the system will send an alert immediately so you can replace the failing disk before data loss occurs.

4. Monthly Periodic Checks

Once a month, hit the Test button. API Tokens can expire, or Email App Passwords might change without you remembering to update them. Don’t wait for a real incident to find out your alerting system has… ‘fallen asleep’.

Conclusion

The Notification Framework on Proxmox VE isn’t just a feature; it’s peace of mind for the administrator. With just 15 minutes of setup, you can take your eyes off the Dashboard while still keeping a pulse on the system. Good luck with your deployment, and may you have many uninterrupted nights of sleep!