Acknowledge and hand over alerts, incident timelines, and built-in database backups
- Alerts can be acknowledged (note, assignee, duration); acknowledged alerts are left out of what needs attention (sidebar, dashboard strip, cards) but stay raised and counted by /metrics - Incidents: each time an alert is raised and goes away is recorded (alert_acks, alert_incidents, incident_notes, migration 0032), with a timeline of acks, maintenance, changes, update runs, related alerts and notes; Incidents page and a digest section - Backups of Homelab Manager's own database: daily checked VACUUM INTO copies, retention, download, check, upload, delete, and restore staged and applied at start-up before the database opens (pre-restore copy kept); alerts and /metrics for stale or failing backups - Docs: README, BACKUP, DATABASE, NOTIFICATIONS, ROLES, API; tests Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
This commit is contained in:
1 parent
7a5b623444
commit
2744a84719
41 files changed
+6573
-26
No files matched your search
@@ -74,7 +74,9 @@ export function useAlertsReport(): State & { reload: () => void } {
|
||||
/** What the sidebar shows next to Alerts: how many problems are active, coloured by the worst one. Silenced and informational ones don't count. */
|
||||
export function alertBadge(report: AlertsReport | null): { count: number; level: "critical" | "warning" } | null {
|
||||
if (!report) return null;
|
||||
const count = report.counts.critical + report.counts.warning;
|
||||
// What still needs somebody to look: alerts somebody has acknowledged don't count here (they are still on the Alerts page, marked).
|
||||
const c = report.counts.attention ?? report.counts;
|
||||
const count = c.critical + c.warning;
|
||||
if (count === 0) return null;
|
||||
return { count, level: report.counts.critical > 0 ? "critical" : "warning" };
|
||||
return { count, level: c.critical > 0 ? "critical" : "warning" };
|
||||
}
|
||||
Reference in new issue
Block a user