Metric Alert Rules
Metric alerts monitor your server's performance data and notify you when thresholds are breached. These are evaluated by the backend on a schedule (every 1-5 minutes).
How They Work
A background job periodically checks all enabled alert rules against recent metric data. If a condition holds for the configured duration, the alert triggers and notifications are sent.
Backend cron (every 1-5 min)
→ Fetch all enabled rules
→ For each rule, check recent metrics
→ If condition met for N minutes → trigger alert
→ If condition no longer met → auto-resolve
Creating a Rule
Go to Dashboard > Monitoring > Alerts tab > Add Rule.
Configuration
| Field | Description | Example |
|---|---|---|
| Name | Human-readable name | "TPS Drop Alert" |
| Metric | What to monitor | TPS, MSPT, CPU, RAM, Player Count, Entity Count, Offline |
| Condition | Below or above threshold | Below 18 |
| Threshold | The trigger value | 18.0 |
| Duration | How long the condition must hold | 3 minutes |
| Cooldown | Minimum time between alerts | 30 minutes |
| Notifications | Where to send alerts | In-app, Email, Discord |
Available Metrics
| Metric | Typical Condition | Example Threshold |
|---|---|---|
| TPS | Below | 18 (warning), 15 (critical) |
| MSPT | Above | 100ms |
| CPU Usage | Above | 80% |
| RAM Usage (MB) | Above | 14000 (for 16GB server) |
| Player Count | Above | 90 (near capacity) |
| Entity Count | Above | 50000 |
| Offline | — | Server unreachable |
The Offline metric is special: it triggers when no heartbeat has been received for the configured duration.
Notification Channels
In-App
A notification appears in your notification bell on the website. Always available.
An HTML email is sent to your account email with alert details, metric values, and a link to the dashboard.
Discord
If your server has a webhook URL configured (in server settings), an embed message is posted to the Discord channel.
Alert Lifecycle
- Triggered — Condition met for the required duration
- Notified — Notifications sent via enabled channels
- Cooldown — No new alerts for this rule during cooldown period
- Resolved — Condition no longer met, auto-resolved with in-app notification
Alert History
The Alert History section shows all past alerts with:
- Rule name and metric
- Condition vs actual value
- Status (triggered / resolved / acknowledged)
- When triggered and when resolved
You can acknowledge active alerts to mark them as seen.