Event Alert Rules
Event alerts trigger **instantly** when matching events are received from your server. Unlike metric alerts (which check on a schedule), event alerts dispatch notifications within milliseconds of the event being reported.
How They Work
Plugin detects TPS drop
→ POST on Voxelbench.com
→ Voxelbench.com stores event
→ Checks all enabled event alert rules for this server
→ Rule matches → instant notification (in-app, email, Discord)
→ Response includes: alerts_dispatched: 1
No cron job, no polling. The notification is sent as part of the same HTTP request that delivers the event.
Creating an Event Alert
Go to Dashboard > Monitoring > Alerts tab > Event Alert Rules section > Add Rule.
Configuration
| Field | Description | Example |
|---|---|---|
| Name | Human-readable name | "Critical Alerts" |
| Event Type | Match a specific type, or "All" | tps_drop, ban, or All |
| Category | Match a category, or "All" | lifecycle, moderation, or All |
| Source | Match a source, or "any" | voxelbench, litebans, or any |
| Min Severity | Minimum severity threshold | info, warning, or error |
| Cooldown | Minimum time between notifications | 5 minutes |
| Notifications | Where to send | In-app, Email, Discord |
Matching Logic
A rule matches an event when ALL specified criteria are met:
- Type: if set, event type must match exactly
- Category: if set, event category must match exactly
- Source: if set, event source must match exactly
- Severity: event severity must be ≥ the minimum (
info<warning<error)
Setting a field to "All" / "any" means it matches anything.
Example Configurations
"Notify me of all critical issues"
- Type: All
- Category: All
- Source: any
- Min Severity: error
- Channels: Email + Discord
→ Catches: tps_critical, memory_critical, any error-severity event
"Ban notifications"
- Type:
ban - Category: All
- Source: any
- Min Severity: info
- Channels: Discord
→ Catches: every ban from LiteBans or any other moderation plugin
"Performance warnings from VoxelBench"
- Type: All
- Category:
lifecycle - Source:
voxelbench - Min Severity: warning
- Channels: In-app
→ Catches: tps_drop, gc_major, memory_high, server_stop
"Anticheat alerts"
- Type: All
- Category:
security - Source: any
- Min Severity: warning
- Channels: Discord + Email
→ Catches: flags from Matrix, Vulcan, Grim, or any anticheat plugin
Cooldown
After a rule triggers, it won't trigger again for the configured cooldown period (default: 5 minutes). This prevents notification spam when many events arrive quickly (e.g., anticheat flagging the same player repeatedly).
Metric Alerts vs Event Alerts
| Metric Alerts | Event Alerts | |
|---|---|---|
| Trigger | Cron checks metrics every 1-5 min | Instant on event reception |
| Latency | 1-5 minutes | < 1 second |
| Best for | Sustained conditions (TPS low for 3 min) | Discrete occurrences (ban, restart, flag) |
| Detection | Backend analyzes metric data | Plugin detects and reports |
| Config | Metric + condition + threshold + duration | Type + category + source + severity |
| Max rules | 3 (Pro) / unlimited (Enterprise) | 10 per server |
Use both together for comprehensive coverage: metric alerts for sustained performance issues, event alerts for immediate notifications on specific occurrences.