root
f5175f1ce0
- audit/phase-one + phase-two: security audit briefs, findings, credential-rotation plan, Docker-USER hardening scripts, rollback refs - disaster-recovery/restore-test-log.md + backup-dr-audit-2026-08-10.md - clients/ (modelortho SEO audit, ai-biz-dev competitive landscape), notes/ (tiktok strategy) - projects/: front-desk-voice-agent, seo-visibility-checker product plan, hotnow-savannah HTML, resend-transactional-email, backup-dashboard-enhancements, code-review-graph, seo-ci-architecture - proposals/verdicttank/: architecture v4.0, methodology, judge-pool review, consolidation reasoning, cross-check review - docs/super-search/firecrawl-provider-strategy.md - updates: CHANGELOG, model-chain, projects-master-readme, intelsight.io - .gitignore: exclude nested standalone repos (seo-tool, venturebuilt)
1.0 KiB
1.0 KiB
Backup Dashboard Enhancements (Queued)
Problem
The Backups tab tells you WHAT is wrong but not enough to investigate or fix it.
Plan
1. Per-item expandability
Click any critical/warning row to expand:
- Server (which box)
- Service name
- Last OK timestamp + days stale
- Actual error message from logs
- Suggested fix based on error pattern
2. Server context tags
Every health check item tagged with origin server. Cross-reference with live server status from Uptime Kuma.
3. Issue age / staleness
Show "3 days ago" vs "2 weeks ago" — stale issues are different from fresh ones.
4. One-click investigation links
- Open the exact log file for that backup job
- Server's Uptime Kuma status page
- The backup script itself (read-only view)
5. Recurrence tracking
Track failure history per check. Flag: "⚠️ 3rd failure in 14 days → escalating"
Implementation
All additive — same JSON, richer fields. Health monitor script needs to collect more metadata per check.
Status
Queued 2026-08-10. Not scheduled.