27 lines
1.0 KiB
Markdown
27 lines
1.0 KiB
Markdown
---
|
|
title: AIOps Alert Scope Control
|
|
keywords: [alert payload, unrelated active alerts, scope control]
|
|
summary: Keep diagnosis scoped to the request payload and avoid diagnosing unrelated active alerts.
|
|
category: aiops
|
|
source: aiops-alert-scope-control
|
|
breadcrumb: AIOps > Alert Scope Control
|
|
kb_scope: rag-eval
|
|
covers: [alert scope, payload, active alerts]
|
|
when_to_retrieve: 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:
|
|
|
|
1. Treat the provided payload as the primary incident boundary.
|
|
2. Use unrelated active alerts only as correlation evidence when they share service, dependency, time window, or trace context.
|
|
3. Do not replace the requested alert with a louder but unrelated alert.
|
|
|
|
This runbook anchors payload, unrelated active alerts, and scope behavior.
|