Files

1.8 KiB

Evidence: aiops-traceable-diagnosis-entry

Local Impact Analysis

  • ChatController.aiOps() is the only caller of AiOpsService.executeAiOpsAnalysis(...).
  • ChatController.aiOps() is the only caller of AiOpsService.extractFinalReport(...).
  • AIOpsRequest exists but only has userRequest; no current controller consumes it.
  • DiagnosisTraceService is flow-agnostic and reads persisted session/step/tool records by sessionId.

GitNexus

GitNexus MCP tools were not exposed in this session. The user explicitly approved skipping GitNexus for this change. Local impact analysis and targeted tests are used instead.

Expected Verification

  • Focused unit tests for AIOps request/session/report helper behavior.
  • Compile verification.
  • OpenSpec validation if CLI is available.

Verification Results

  • openspec.cmd validate aiops-traceable-diagnosis-entry --strict: passed.
  • mvn -q "-Dtest=AiOpsServiceTest,DiagnosisTraceServiceTest" test: passed after rerun with approved Maven access.
  • mvn -q -DskipTests compile: passed.

Demo Alignment

  • Added knowledge_base/troubleshooting/aiops-alert-runbook.md so mock AIOps alerts have matching knowledge-base guidance.
  • Aligned the documented AIOps demo with mock data: HighCPUUsage on payment-service, using system-metrics evidence.

Metric Alignment Follow-up

  • Runtime verification showed diagnosis_session.tool_call_count counted agent steps with tool calls, while trace returned actual tool_invocation records.
  • Updated ChatService and AiOpsService metric backfill to use ToolInvocationRepository.countBySessionId(sessionId).
  • Targeted verification:
    • mvn -q "-Dtest=AiOpsServiceTest,ChatServiceSequentialAgentTest,DiagnosisTraceServiceTest" test: passed.
    • mvn -q -DskipTests compile: passed.