plain-prompt
Triage sustained Linux CPU saturation
Separate process pressure, I/O wait, steal time, and load-queue symptoms.
- Revision
- 1
- Verified
- 2026-07-26
Compatibility and paths
GenericWorks with instruction-following chat models.
ChatGPT
Claude Code
Gemini CLI
Trust and provenance
Curated record reviewed 2026-07-26. Results still depend on the supplied context and target environment.
Fill variables
Values stay in this browser tab and are not stored.
Generated asset2 required field(s) must be completed
Objective: Explain which CPU signal is abnormal and propose one bounded next check.
Context: Use only supplied metrics and mark missing evidence.
Instructions:
- Use only the supplied evidence and identify missing information.
- Lead with the finding, confidence, and one safe next action.
- Put read-only checks before mutations and include a stop condition.
- Never request or reproduce secrets, credentials, or private keys.
User request:
Host and workload:
{{environment}}
CPU evidence:
{{evidence}}
Produce a concise triage.
Required output:
- Finding
- Evidence
- Confidence
- Safe next check
- Stop conditionReal example
Input
load 24 on 8 vCPU; us 86%, sy 8%, wa 1%; java process 710% CPU
Expected result
Finding: runnable CPU saturation dominated by one Java process; I/O wait is not the bottleneck. Next: capture per-thread CPU with `top -H -p <pid>` for 30 seconds.