docs(monitoring): record t102 target freshness rollout [skip ci]

This commit is contained in:
Your Name
2026-05-20 13:01:49 +08:00
parent cbb0221f0f
commit ce0d6a75c4
2 changed files with 6 additions and 80 deletions

View File

@@ -2394,13 +2394,13 @@ Phase 6 完成後
- 技術債post-deploy monitoring coverage 仍顯示 `awoooi_alert_chain_last_success_timestamp` 指標缺失non-critical與 Prometheus target freshness 噪音;同輪 health / rollout / E2E 皆通過,但監控 scrape / target state 需要後續清理。
- 目前進度更新AwoooP 告警可觀測鏈約 99.5%;低風險自動修復閉環約 95.2%;前端 AI 自動化管理介面同步約 99.6%;治理告警可讀性 / 可處置性約 99.4%AI Agent ownership 可追溯性約 98.4%KM healthcheck 派工可追蹤性約 99.8%Hermes KB growth 草稿 / owner review 閉環約 99.7%;完整 AI 自動化管理產品化約 98.4%。
**T102 Post-deploy monitoring coverage target freshness cleanup2026-05-20 台北)**
**T102 Post-deploy monitoring coverage target freshness 穩定化2026-05-20 台北)**
- 觸發T101 post-deploy coverage 曾短暫看到 `awoooi-api` target down但 production health / rollout / E2E 皆通過live 110 Prometheus 驗證 `awoooi-api` UP、coverage 100%,根因是 coverage gate 單次讀 Prometheus `activeTargets`,會被 rollout / scrape freshness 瞬間值誤導。
- 修正:`scripts/generate_monitoring.py --check` 新增 Prometheus target stabilization遇到 `real_down_jobs``missing_expected` 會短時間重查transient drift 清掉才放行persistent DOWN 仍 fail。新增 CLI/env attempts + sleep seconds並改用 `urllib` 取代 `requests`,讓 operator 無 venv 也能跑。
- 測試 / hygiene新增 `test_generate_monitoring_stabilization.py` 覆蓋 transient DOWN、missing expected、persistent DOWN、clean snapshot測試載入 script 時關閉 bytecode避免 `scripts/__pycache__` cleanup noise。B5 cleanup 擴到整個 `tests` tree未來實際 CD 會清 shared helper pycache。
- 邊界:沒有把 `awoooi-api` 白名單化API 真 DOWN 仍會紅燈;本輪不改 incident / approval / auto-repair / AI router / frontend runtime 行為。剩餘 act-runner `errSymlink` cleanup warning 是 runner hygienemonitoring coverage false red
- Production / CI`8fa8d690 fix(monitoring): stabilize post-deploy target coverage``6e5d68ee test(monitoring): avoid script bytecode cleanup noise``89f39759 ci: clean b5 test bytecode artifacts` 已推 Gitea maindeploy marker `f542aa52 chore(cd): deploy 6e5d68e [skip ci]`Gitea Code Review `2596` / `2599` / `2600` successCD `2598` tests / build-and-deploy / post-deploy-checks 全 success。Post-deploy Monitoring Coverage Check 顯示 coverage 100.0%、real_down_jobs=0、`awoooi-api` UPPlaywright E2E 5 passedCI/CD success notification mirrored through AWOOI API / AwoooP
- 目前進度更新AwoooP 告警可觀測鏈約 99.65%Monitoring coverage gate 準確性約 99.7%;低風險自動修復閉環約 95.2%;前端 AI 自動化管理介面同步約 99.6%;完整 AI 自動化管理產品化約 98.5%。
- 修正:`scripts/generate_monitoring.py --check` 新增 Prometheus target stabilization遇到 `real_down_jobs``missing_expected` 會短時間重查transient drift 清掉才放行persistent DOWN 仍 fail。新增 CLI/env attempts + sleep seconds並改用 `urllib` 取代 `requests`,讓 operator 無 venv 也能跑;空的 known-down 段落不再輸出
- 測試 / hygiene新增 `test_generate_monitoring_stabilization.py` 覆蓋 transient DOWN、missing expected、persistent DOWN、clean snapshot測試載入 script 時關閉 bytecode避免 `scripts/__pycache__` cleanup noise。B5 cleanup 擴到整個 `tests` tree避免 shared helper pycache 留在 act runner workspace
- 邊界:沒有把 `awoooi-api` 白名單化API 真 DOWN 仍會紅燈;本輪不改 incident / approval / auto-repair / AI router / frontend runtime 行為。`awoooi_alert_chain_last_success_timestamp` SLO emitter 缺口仍non-critical 技術債,另列後續
- Production / CI`8fa8d690 fix(monitoring): stabilize post-deploy target coverage``6e5d68ee test(monitoring): avoid script bytecode cleanup noise``89f39759 ci: clean b5 test bytecode artifacts` 已推 Gitea maindeploy marker `f542aa52 chore(cd): deploy 6e5d68e [skip ci]`Actions#1911 Code Review success 10s、#1910 CD success 7m17s、#1913 Code Review success 10s、#1912 CD success 9m20s、#1914 Code Review success 12s。Post-CD smokehealth healthy/prod/mock_mode=falseMonitoring Coverage Check coverage 100.0%、real_down_jobs=0、`awoooi-api` UPPlaywright E2E 5 passed。
- 目前進度更新AwoooP 告警可觀測鏈約 99.7%Monitoring coverage gate 準確性約 99.7%;低風險自動修復閉環約 95.2%;前端 AI 自動化管理介面同步約 99.6%;完整 AI 自動化管理產品化約 98.6%。
---