SuperBizAgent-java/devflow/projects/2026-07-04-aiops-alert-scope-control/evidence.md

Evidence: aiops-alert-scope-control

Local Impact Analysis

• AiOpsService.buildTaskPrompt(...) is used by executeAiOpsAnalysis(...).
• No controller, DTO, repository, or database changes are required.
• Existing AiOpsServiceTest already exercises request summary helpers and can be extended for scope prompt rules.

Verification Results

• mvn -q "-Dtest=AiOpsServiceTest" test passed.
• mvn -q -DskipTests compile passed.
• openspec.cmd validate aiops-alert-scope-control --strict passed.

Runtime Verification

• Runtime session: mvp-demo-aiops-payment-cpu-codex-scope-003.
• /api/ai_ops SSE emitted the requested session message and finished with done.
• diagnosis_session persisted:
  • agent_flow = AI_OPS
  • status = SUCCESS
  • total_duration_ms = 69875
  • step_count = 5
  • tool_call_count = 8
• Tool invocation counts:
  • query_metrics = 1
  • lookup_knowledge = 1
  • query_logs = 6
• Report scope check:
  • 告警根因分析 - HighCPUUsage exists.
  • 告警根因分析 - HighMemoryUsage does not exist.
  • 告警根因分析 - SlowResponse does not exist.
  • 相关风险告警 exists.

Runtime Fix

• Added Hikari settings in src/main/resources/application.yml after the first runtime attempt failed on stale MySQL pool connections:
  • maximum-pool-size: 5
  • minimum-idle: 1
  • connection-timeout: 10000
  • validation-timeout: 5000
  • idle-timeout: 60000
  • max-lifetime: 120000
  • keepalive-time: 30000