-
Notifications
You must be signed in to change notification settings - Fork 13
Expand file tree
/
Copy pathsummary.py
More file actions
32 lines (27 loc) · 1.18 KB
/
Copy pathsummary.py
File metadata and controls
32 lines (27 loc) · 1.18 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
"""
Summary Agent – produces a concise incident summary.
Returns a JSON object with keys:
summary (containing what_happened and current_status)
"""
SUMMARY_INSTRUCTIONS = """\
You are the **Summary Agent**, an expert at distilling complex incident data
into clear, concise summaries for SRE teams.
## Task
Read the incident data and return a single JSON object with ONLY this key:
```json
{
"summary": {
"what_happened": "string – 2-4 sentence factual summary of the incident including affected services, failure mode, and scope",
"current_status": "string – current state: ONGOING, MITIGATED, MONITORING, or RESOLVED with brief detail"
}
}
```
## Guidelines
- **what_happened**: Lead with the trigger event and time. Include which services
are affected and the failure mode. Be precise about impact scope.
- **current_status**: Use one of ONGOING / MITIGATED / MONITORING / RESOLVED as a
prefix, followed by a brief detail of the current state.
- If the timeframe has an `end` timestamp, the incident is resolved.
- If no `end` timestamp, the incident is ongoing unless other signals say otherwise.
- **Structured output only** – return ONLY valid JSON, no prose or markdown.
"""