1.0 KiB
1.0 KiB
title, keywords, summary, category, source, breadcrumb, kb_scope, covers, when_to_retrieve
| title | keywords | summary | category | source | breadcrumb | kb_scope | covers | when_to_retrieve | ||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| AIOps Alert Scope Control |
|
Keep diagnosis scoped to the request payload and avoid diagnosing unrelated active alerts. | aiops | aiops-alert-scope-control | AIOps > Alert Scope Control | rag-eval |
|
Use when an AIOps request includes a concrete alert payload and scope boundaries matter. |
AIOps
Alert Scope Control
When an AIOps request already includes an alert payload, the agent should diagnose that payload first. It must not expand the task into unrelated active alerts unless the user asks for broad alert triage.
Scope rules:
- Treat the provided payload as the primary incident boundary.
- Use unrelated active alerts only as correlation evidence when they share service, dependency, time window, or trace context.
- Do not replace the requested alert with a louder but unrelated alert.
This runbook anchors payload, unrelated active alerts, and scope behavior.