fix(reboot): route slo blockers to action matrix
Some checks failed
CD Pipeline / workflow-shape (push) Successful in 0s
CD Pipeline / cancel-stale-cd (push) Has been skipped
CD Pipeline / tests (push) Successful in 59s
CD Pipeline / build-and-deploy (push) Successful in 4m40s
CD Pipeline / post-deploy-checks (push) Has been cancelled

This commit is contained in:
Your Name
2026-07-03 00:33:27 +08:00
parent f700489bb9
commit fd79a8cd0c
8 changed files with 630 additions and 10 deletions

View File

@@ -223,8 +223,8 @@ groups:
auto_repair: "false"
annotations:
summary: "重啟恢復 SLO blocker 未清除:{{ $labels.blocker }}"
description: "reboot-auto-recovery scorecard 仍有 active blocker={{ $labels.blocker }};不可只看總 blocker_count必須對應處理 99/VMware、主機可達、service/backup/Wazuh 或 public fallback 的具體證據。"
runbook: "先讀 110 最新 /home/wooo/reboot-recovery/reboot-auto-recovery-slo-*/scorecard.jsonsummary.txt、host-probe.txt 與同 run 的 public-maintenance/windows99 readbackWindows99 只走 no-secret collector 或 console verifybackup 只讀 backup-status/exporterWazuh 只讀 registry/API禁止 reboot、Docker/systemd/Nginx/DB/firewall restart、restore/prune/delete。"
description: "reboot-auto-recovery scorecard 仍有 active blocker={{ $labels.blocker }}category={{ $labels.category }}、owner_lane={{ $labels.owner_lane }}、primary={{ $labels.primary }}。不可只看總 blocker_count必須依 action matrix 處理 99/VMware、主機可達、service/backup/Wazuh、CPU pressure 或 public fallback 的具體證據。"
runbook: "先讀 110 最新 /home/wooo/reboot-recovery/reboot-auto-recovery-slo-*/scorecard.json 的 active_blocker_action_matrix再讀 summary.txt、host-probe.txt 與同 run 的 public-maintenance/windows99 readbackWindows99 只走 no-secret collector 或 console verifybackup 只讀 backup-status/exporterWazuh 只讀 registry/API禁止 reboot、Docker/systemd/Nginx/DB/firewall restart、restore/prune/delete。"
- alert: RebootAutoRecoveryActiveBlockerMetricMissing
expr: |