Alerts
The Alerts feature requires an Enterprise license. If you are on a Community or Starter plan, this page will display an upgrade prompt. See Plans & Pricing for details.
The Alerts page provides a real-time alert dashboard for monitoring resource utilization and event-based anomalies across your Proxmox infrastructure. Alerts are processed by the ProxCenter orchestrator and displayed with configurable thresholds and rules.
Overview
The Alerts page is organized into three tabs:
- Alerts -- View and manage active alerts
- Thresholds -- Configure resource utilization thresholds
- Event Rules -- Create custom rules that trigger alerts based on Proxmox events
Alert Dashboard
Summary Statistics
Four stat cards at the top provide a quick overview:
| Stat | Description |
|---|---|
| Active Alerts | Total number of currently active (unresolved) alerts |
| Critical | Number of alerts with critical severity |
| Warnings | Number of alerts with warning severity |
| Acknowledged | Number of alerts that have been acknowledged but not yet resolved |
Alert List
The alert data grid displays all alerts with the following columns:
| Column | Description |
|---|---|
| Severity | Info, Warning, or Critical |
| Status | Active, Acknowledged, or Resolved |
| Message | Alert description with occurrence count |
| Resource | The affected resource (node, VM, storage) |
| Value | Current metric value that triggered the alert |
| Last Seen | When the alert was last detected |
| Actions | Acknowledge or Resolve buttons |
Filtering Alerts
You can filter the alert list by:
- Search -- Free text search across alert messages and resource names
- Status -- Active, Acknowledged, Resolved, or All
- Severity -- Critical, Warning, Info, or All
Managing Alerts
Each active alert can be managed individually:
- Acknowledge -- Mark an alert as seen without resolving it. This is useful to indicate you are aware of the issue.
- Resolve -- Mark an alert as resolved. Resolved alerts remain in the history for reference.
You can also use the Resolve All button to resolve all currently active alerts at once.
Resolving an alert does not fix the underlying issue. If the condition persists (e.g., CPU usage remains above the critical threshold), a new alert will be generated.
Thresholds
The Thresholds tab lets you configure at what resource utilization levels alerts should be triggered. Each resource type has two levels:
CPU Thresholds
- Warning -- Default: 80%
- Critical -- Default: 95%
Memory Thresholds
- Warning -- Default: 85%
- Critical -- Default: 95%
Storage Thresholds
- Warning -- Default: 80%
- Critical -- Default: 90%
Use the slider controls to adjust warning and critical thresholds for each resource type. Click Save to apply your changes.
Set your warning thresholds low enough to give you time to react before a resource becomes critically exhausted. For storage, consider setting warning at 75% if your storage grows rapidly.
Event Rules
Event rules allow you to create custom alert triggers based on Proxmox task and log events. This provides granular control over what generates an alert.
Creating a Rule
Click the Add button to open the rule creation dialog. Configure the following fields:
| Field | Description |
|---|---|
| Name | A descriptive name for the rule (required) |
| Description | Optional explanation of what the rule monitors |
| Category | Filter by event category: All, Tasks only, or Logs only |
| Event Level | Filter by event severity: All, Error, Warning, or Info |
| Task Types | Comma-separated list of task types to match (leave empty for all) |
| Pattern | Optional regex pattern to match against event messages |
| Alert Severity | The severity of the generated alert: Info, Warning, or Critical |
| Email Notification | Whether to send an email when this rule triggers |
| Active | Enable or disable the rule |
Managing Rules
The rules data grid shows all configured rules with their current state. For each rule you can:
- Toggle the rule on/off with the switch in the first column
- Edit the rule to modify any field
- Delete the rule with confirmation
Rule Examples
- Monitor all error-level tasks: Set Category to "Tasks", Event Level to "Error", Alert Severity to "Critical"
- Watch for backup failures: Set Category to "Tasks", Task Types to "vzdump", Event Level to "Error"
- Pattern-based monitoring: Set Pattern to
WARNINGS:to catch tasks that complete with warnings
Alert Lifecycle
- The orchestrator evaluates thresholds and event rules every 30 seconds
- When a condition is met, an alert is created with status Active
- If the same condition triggers again, the existing alert's occurrence count increments and the "last seen" timestamp updates
- An operator can Acknowledge the alert to indicate awareness
- The alert is eventually Resolved either manually or when the condition clears
Orchestrator Connection
Alerts require the ProxCenter orchestrator service to be running. If the orchestrator is unavailable, a warning banner will appear at the top of the page. The orchestrator handles:
- Periodic resource monitoring across all connected nodes
- Event stream analysis against configured rules
- Alert creation, deduplication, and lifecycle management