Alert rules of your own, storage forecasts for Proxmox and Synology, and snooze
- Monitoring -> Alert rules: CPU, memory, disk use and disk temperature limits with a time, severity and scope (all, one server, a tag); try before saving; findings are ordinary health conditions - Proxmox storages and Synology volumes are written down on each health pass (hourly, 400 days) and forecast like server disks: badge and history chart on the pages, alert, digest line, /metrics gauge - Snooze an alert until a time; held back like maintenance, messages held, announced once again if still there when it ends - Docs updated Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
This commit is contained in:
1 parent
788b3e073c
commit
24ae8db380
38 files changed
+7847
-8
No files matched your search
@@ -74,6 +74,7 @@ export function mostWithin(times: number[], windowMs: number): number {
|
||||
/** What to try, from the kind of alert and the key it has. Plain advice; nothing it says is done for anyone. */
|
||||
export function hintFor(category: string, alertId: string): string {
|
||||
const key = keyOfAlertId(alertId, category);
|
||||
if (key.startsWith("rule:")) return "A limit of your own (Monitoring → Alert rules): if it keeps coming back, raise the limit or make it hold for longer before it raises.";
|
||||
if (key.startsWith("new-port:")) return "If this port should be listening, mark it as expected on the server's Ports card.";
|
||||
if (key.startsWith("heartbeat")) return "If the job is just sometimes late, give its heartbeat more grace; if it fails, look at what it printed.";
|
||||
if (key.startsWith("endpoint:")) return "Raise “Alert after … failures in a row” on the check, or its timeout or interval — or fix what is making it fail.";
|
||||
|
||||
Reference in new issue
Block a user