docs: clarify difference between pulse-no-alerts and pulse-monitor-only

- pulse-no-alerts: completely silent, no alerts generated at all
- pulse-monitor-only: alerts show in UI for manual checking, but no notifications sent
- updated descriptions to make the distinction clearer
- improved use case examples to show when to use each
This commit is contained in:
Pulse Monitor
2025-08-20 14:54:38 +00:00
parent 6e6fc1b03a
commit dfcfc4f857
2 changed files with 7 additions and 7 deletions
+5 -5
View File
@@ -292,8 +292,8 @@ Control alerts directly on VMs/containers using Proxmox tags - perfect for both
| Tag | Purpose | Use Case |
|-----|---------|----------|
| `pulse-no-alerts` | Disable all alerts | VMs that shouldn't alert (dev, testing, or special workloads) |
| `pulse-monitor-only` | Monitor without notifications | See metrics in UI but don't get paged |
| `pulse-no-alerts` | Completely silent | No alerts in UI, no notifications - for VMs you don't monitor |
| `pulse-monitor-only` | UI alerts only | Shows alerts in dashboard but no emails/webhooks - check manually |
| `pulse-relaxed` | Higher thresholds (95%/98%) | Services that naturally run hot (databases, media servers) |
**When to use tags vs custom rules:**
@@ -302,13 +302,13 @@ Control alerts directly on VMs/containers using Proxmox tags - perfect for both
**Common permanent uses:**
```bash
# TrueNAS/Samba servers with aggressive caching
# TrueNAS/Samba servers with aggressive caching - higher thresholds
pvesh set /nodes/pve/lxc/100/config -tags 'truenas,pulse-relaxed'
# Development VMs that shouldn't page anyone
# Test/dev VMs - completely ignore, don't track alerts
pvesh set /nodes/pve/qemu/200/config -tags 'dev,pulse-no-alerts'
# Staging environment - monitor but don't notify
# Production staging - see problems in UI but don't wake anyone up
pvesh set /nodes/pve/lxc/300/config -tags 'staging,pulse-monitor-only'
```
+2 -2
View File
@@ -701,8 +701,8 @@ function OverviewTab(props: { overrides: Override[]; activeAlerts: Record<string
Add these tags to any VM/CT in Proxmox to control alert behavior without navigating to Pulse:
</p>
<ul class="space-y-1 text-xs text-green-700 dark:text-green-300">
<li><code class="bg-green-100 dark:bg-green-900/50 px-1 py-0.5 rounded">pulse-no-alerts</code> - Disable all alerts for maintenance or special VMs</li>
<li><code class="bg-green-100 dark:bg-green-900/50 px-1 py-0.5 rounded">pulse-monitor-only</code> - Show in UI but don't send notifications</li>
<li><code class="bg-green-100 dark:bg-green-900/50 px-1 py-0.5 rounded">pulse-no-alerts</code> - Completely silent - no alerts in UI or notifications</li>
<li><code class="bg-green-100 dark:bg-green-900/50 px-1 py-0.5 rounded">pulse-monitor-only</code> - Shows alerts in UI but won't email/page you</li>
<li><code class="bg-green-100 dark:bg-green-900/50 px-1 py-0.5 rounded">pulse-relaxed</code> - Use higher thresholds (95% CPU/RAM, 98% disk)</li>
</ul>
<p class="text-xs text-green-600 dark:text-green-400 mt-2">