Skip to main content

Notifications

ProxCenter can send notifications when important events occur in your infrastructure -- alerts firing, backups failing, tasks completing, or compliance scans detecting issues. Notifications are delivered via email or webhooks.

Overview

Notifications are triggered by events in ProxCenter. You configure notification channels (where to send) and then associate them with the event types you care about. Multiple channels can receive the same event, and each channel can be filtered to only specific severity levels.

Notification Channels

Email

Send notifications to one or more email addresses. ProxCenter uses SMTP to deliver emails.

FieldDescription
SMTP HostYour mail server address
SMTP PortPort number (587 for STARTTLS, 465 for SSL, 25 for plain)
UsernameSMTP authentication username
PasswordSMTP authentication password
From AddressThe sender email address
RecipientsComma-separated list of recipient email addresses
Use TLSEnable TLS encryption

Webhooks

Send notifications as HTTP POST requests to any URL. The payload is a JSON object containing the event type, severity, message, and metadata.

FieldDescription
URLThe webhook endpoint to receive POST requests
HeadersOptional custom headers (e.g., Authorization: Bearer <token>)
SecretOptional shared secret for HMAC signature verification

Webhooks integrate with:

  • Slack -- Use an Incoming Webhook URL
  • Microsoft Teams -- Use a Teams Incoming Webhook connector
  • Discord -- Use a Discord webhook URL
  • PagerDuty -- Use the Events API v2 endpoint
  • Custom systems -- Any HTTP endpoint that accepts JSON POST requests

Event Types

EventDescription
Alert triggeredA threshold alert has fired (CPU, memory, storage, etc.)
Alert resolvedA previously triggered alert has returned to normal
Backup failedA backup job failed on a connected PBS or PVE instance
Task failedA Proxmox task completed with an error
Node offlineA Proxmox node has become unreachable
Connection lostA ProxCenter connection to a Proxmox instance is down
Compliance issueA compliance scan found new critical or high findings
CVE detectedA CVE scan found new critical vulnerabilities

Configuration

  1. Navigate to Settings > Notifications
  2. Add a notification channel (email or webhook)
  3. Test the channel using the Send Test button
  4. Select which event types should trigger notifications on this channel
  5. Optionally set a minimum severity level to reduce noise
tip

Start with critical events only (node offline, backup failed, connection lost) and expand as needed. Too many notifications lead to alert fatigue.

Enterprise Feature

Notifications are available in the Enterprise edition.

Permissions

PermissionDescription
settings.manageRequired to configure notification channels and rules