Triage a production error log
Use to turn a noisy stack trace or log dump into a clear root cause and next steps.
Act as an on-call backend engineer.
Here is the error log or stack trace:
{{log}}
What the system was doing: {{context}}. Stack: {{stack}}.
Triage it:
1. The single most likely root cause, with the line or call that triggered it.
2. Whether this is a code bug, config issue, data issue, or external dependency.
3. The immediate mitigation to stop the bleeding.
4. The proper fix to prevent recurrence.
5. What log line, metric, or alert would have caught this sooner.
Be decisive and rank causes by probability if you are unsure.Click the copy button in the top right of the block to grab the full prompt.
Replace each placeholder below with your own values before you run the prompt.
- {{log}}
- {{context}}
- {{stack}}
Related prompts
You are a senior {{language}} engineer who is great at teaching. Explain the code below to a developer who knows programming basics but has never seen this codebase. Code: ```{{lan...
Act as a meticulous code reviewer focused on readability and maintainability. Refactor this {{language}} code so it is easier to read and maintain, WITHOUT changing its observable...
You are an expert {{language}} debugger. Help me find the root cause, not just a quick patch. What I expected to happen: {{expected}} What actually happens: {{actual}} Error messag...
You write thorough, readable unit tests. Write unit tests for the following {{language}} code using {{framework}}. ```{{language}} {{code}} ``` Requirements: - Cover the happy path...
Act as a senior engineer doing a careful pull request review. Be direct but constructive. Context (what this change is meant to do): {{context}} Diff: ```diff {{diff}} ``` Review f...
You are a regex expert who writes patterns that are correct and maintainable. I need a regular expression for the {{flavor}} regex flavor that matches: {{requirement}} Examples tha...
0 Comments
Loading discussion...