plain-prompt
Correlate multi-service incident logs
Build a timestamped evidence chain without merging unrelated errors.
- 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: Identify the earliest shared failure signal across services.
Context: Normalize time zones and retain source attribution.
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:
Systems/time zone:
{{environment}}
Log excerpts:
{{evidence}}
Build a correlation table.
Required output:
- Finding
- Evidence
- Confidence
- Safe next check
- Stop conditionReal example
Input
12:01 proxy upstream timeout; 12:00:58 app pool exhausted; 12:00:42 database connections 100/100
Expected result
Earliest shared signal: database connection saturation at 12:00:42, followed by application pool exhaustion and proxy timeout. Validate with connection acquisition latency and pool limits.