Files
awoooi/apps/api
OG T 7db8845cbb
All checks were successful
CD Pipeline / build-and-deploy (push) Successful in 12m59s
fix(asset_scanner+coverage): host_service→monitoring_target (CHECK violation 修) + log 補 4 維
2 個 bug 修復 + 實證驗證:

1. asset_scanner: host_service 不在 asset_inventory CHECK 允許列表
  ceb61c3 部署後 Pod log: CheckViolationError 'asset_inventory_type_valid'
  詳: '192.168.0.125:32334' 寫入時 asset_type='host_service' 被拒
  allowed list: host/container/k8s_workload/k8s_resource/database/...
               monitoring_target/third_party_service/... (27 種)
  修: host_service → monitoring_target (ADR-090 schema 原為 scrape target 預留)

2. coverage_evaluator logger: 只 log 原 3 維 (monitoring/alerting/km)
  導致誤以為 c1f23cf 4 維新 code 沒生效 (實際 DB 已有 auto_playbook/
  remediation/rule_matching/rule_creation 資料)
  修: logger.info 補 playbook/remediation/rule_matching/rule_creation 4 個 kwarg

實證 coverage 7 維 DB 分佈 (已生效):
  auto_alerting:    22 green / 78 red / 52 unknown
  auto_km_creation:  5 green / 17 yellow / 130 unknown
  auto_monitoring:   1 green / 1 red / 150 unknown
  auto_playbook:     3 green / 19 yellow / 130 unknown  ← 新維度
  auto_remediation:  0 / 0 / 98 red / 54 unknown        ← 新維度
  auto_rule_creation: 0 / 0 / 100 red / 52 unknown       ← 新維度
  auto_rule_matching: 4 green / 96 yellow / 52 unknown   ← 新維度

治理洞察:
  98 red remediation = 大部分 asset 過去 30d 沒修復行動 (修復能力缺口)
  100 red rule_creation = 無 AI rule (全 yaml_hardcoded)
  96 yellow rule_matching = 過去 30d 沒告警觸發 (可能沒問題/沒覆蓋)

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-04-19 20:27:48 +08:00
..