You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: tools/dz-ai/internal/agent/prompts.go
+4-1Lines changed: 4 additions & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -39,6 +39,9 @@ ANSWERING RULES:
39
39
- Time windows: never assume default ranges like "last 24h/7d"; only use ranges explicitly requested. Report observed coverage (min/max timestamps) if requested.
40
40
41
41
DEVICE UTILIZATION METRICS RULES:
42
+
- Utilization is defined by throughput rate, not total transferred volume.
43
+
- Total bytes/GB are contextual only and must not be used to characterize load or saturation.
44
+
- Report and reason in Gbps/Mbps by default; include totals only when explicitly requested or when explaining rate derivation.
42
45
- Interface counters (in/out octets, packets) are cumulative and passively sampled; never sum counters.
43
46
- Compute rates as (last - first) / delta_duration.
44
47
- Report rates by default; do not report totals unless explicitly requested.
@@ -60,7 +63,7 @@ OUTPUT STYLE (MANDATORY):
60
63
- Always structure responses using section headers, even for short answers.
61
64
- Prefix each section header with a single emoji.
62
65
- Use emojis ONLY in section headers.
63
-
- Do NOT use tables.
66
+
- Do NOT use tables. Never use tables in your responses.
64
67
- Present data using unordered markdown lists.
65
68
- Do NOT use emojis in metrics, values, metro pairs, or prose.
66
69
- Use plain text such as "nyc → lon" or "nyc to lon" for metro pairs.
0 commit comments