Analyze logs to find what went wrong
Reads logs to identify errors, patterns, and the likely root cause.
The prompt
Analyze these logs and help me find what went wrong.
System and component: [e.g. Nginx, Kubernetes pod, Node API, Windows event log]
What users noticed and when: [SYMPTOM, TIME WINDOW, timezone]
Recent changes: [deploys, config changes, traffic spikes]
Logs:
[PASTE — redact secrets, tokens, and personal data]
Deliver:
1. A timeline of significant events.
2. Errors and warnings grouped by type, with counts and first/last occurrence.
3. Anomalies and correlations (e.g. latency spikes, retries, a resource exhausted just before errors began).
4. The most likely root cause and your confidence level, with the evidence.
5. Next diagnostic steps (exact commands or queries) and a suggested fix.
6. Monitoring or alerting that would have caught this sooner.
Highlighted [brackets] are blanks to replace with your own details.
Fill in the blanks and use this promptMore Software Development prompts
What to fill in
- e.g. Nginx, Kubernetes pod, Node API, Windows event log
- SYMPTOM, TIME WINDOW, timezone
- deploys, config changes, traffic spikes
- PASTE — redact secrets, tokens, and personal data
How this prompt is built
This prompt follows the Few-Shot structure (Few-shot prompting). A few-shot prompt includes one or more worked examples of the input and the output you want, so the model can copy the pattern instead of guessing it.
Related prompts
- Get a beginner-friendly code review of my first projectA ranked set of the five improvements that matter most, explained simply, plus what you did well and what to learn next.
- Make my research analysis reproducible and shareableOrganizes my project's data, code, and documentation so others (and future me) can rerun the analysis and get the same results.
- Audit a codebase for bugs, risks, and tech debtA systematic review of a repository with prioritized findings and a remediation plan.
- Create a test plan and test casesA risk-based test strategy with test cases for functional, integration, and end-to-end testing.