feat: add traceable scoped AIOps diagnosis

2026-07-04 22:57:28 +08:00
parent 246c99b954
commit 23ee05c7c3
32 changed files with 1179 additions and 25 deletions
@@ -0,0 +1,28 @@
+# aiops-alert-scope-control Specification
+
+## Purpose
+TBD - created by archiving change aiops-alert-scope-control. Update Purpose after archive.
+## Requirements
+### Requirement: AIOps payload mode focuses on supplied alert
+When an AIOps request includes alert payload fields, the system SHALL instruct the agent to focus the final alert analysis report on the supplied alert.
+
+#### Scenario: Request includes alertName and service
+- **WHEN** a caller posts to `/api/ai_ops` with `alertName` and `service`
+- **THEN** the AIOps task prompt identifies payload mode
+- **AND** the prompt instructs the agent not to create full root-cause sections for unrelated active alerts
+
+### Requirement: AIOps auto-discovery mode queries active alerts first
+When an AIOps request omits alert payload fields, the system SHALL instruct the agent to first discover active Prometheus alerts.
+
+#### Scenario: Request body is omitted
+- **WHEN** a caller posts to `/api/ai_ops` without alert fields
+- **THEN** the AIOps task prompt identifies auto-discovery mode
+- **AND** the prompt instructs the agent to call `queryPrometheusAlerts` first
+
+### Requirement: Payload mode may use active alerts as supporting context
+Payload mode SHALL allow active-alert lookup as supporting evidence, but SHALL keep unrelated alerts out of the main report sections.
+
+#### Scenario: Prometheus returns multiple active alerts
+- **WHEN** payload mode is active and `queryPrometheusAlerts` returns unrelated active alerts
+- **THEN** the prompt permits mentioning those alerts only as related risk or context
+- **AND** the final report target remains the supplied alert