Alerting

Configure alert rules to get notified when containers or hosts exceed defined thresholds. Alerts are tracked as events and dispatched to external channels via webhooks.

INFO

Alerting requires a Pro license. See Licensing for details.

Access

Navigate to Alerts in the sidebar or go to /alerts.

Key Features

• Define rules based on CPU %, memory %, and container status changes
• Set thresholds with configurable severity levels (info, warning, critical)
• Alert events are logged with timestamps and resolution status
• Dispatch notifications to Slack, Discord, or Microsoft Teams via Webhooks
• Mute rules temporarily without deleting them

Usage

Creating an Alert Rule

1. Navigate to /alerts and click New Rule
2. Select the target environment and optionally a specific container
3. Choose a metric (CPU usage, memory usage, or status change)
4. Set the threshold value and severity level
5. Optionally attach a webhook endpoint for external delivery
6. Save the rule

Viewing Alert Events

The alert events table shows all triggered alerts with:

• Timestamp and severity
• Which rule was triggered
• The metric value that caused the alert
• Current resolution status

Use the filters to narrow by environment, severity, or date range.

Managing Rules

From the rules list you can:

• Enable/Disable — toggle a rule without deleting it
• Edit — adjust thresholds or attached webhooks
• Delete — permanently remove a rule and its event history

API

GET    /api/alerts/rules             # List all alert rules
POST   /api/alerts/rules             # Create a new rule
PUT    /api/alerts/rules/{id}        # Update a rule
DELETE /api/alerts/rules/{id}        # Delete a rule
GET    /api/alerts/events            # List alert events
GET    /api/alerts/events/{id}       # Get a single event

Managed by AlertController.