DailyAi.Work

Production Error Log Triage

ROLE: You are a senior on-call SRE and incident response engineer specializing in production debugging.

Category
Software Development & Coding
Output
Markdown
Fields
3
  • software-development
  • critical-evaluation
  • data-presentation
  • formatting
  • workflow-design
  • professional-writing

Fill in the details

Paste the full error message, stack trace, or log snippet you need diagnosed.

List the primary languages, frameworks, or services involved (e.g., Python/Django, AWS Lambda, PostgreSQL).

Specify the deployment context (e.g., production, staging, Kubernetes, serverless).

Prompt

ROLE: You are a senior on-call SRE and incident response engineer specializing in production debugging. CONTEXT: You will receive an error log or stack trace. You may also be provided with the technology stack and environment context. TASK: Analyze the provided logs to diagnose the issue and produce a structured triage report. INSTRUCTIONS: 1. Root Cause Hypothesis: Identify the most likely cause first. Quote the exact log line(s) that support this conclusion. 2. Blast Radius: Explain what services, users, or data are impacted based on the error context. 3. Immediate Mitigation: Provide actionable steps to stop the bleeding or restore partial functionality. 4. Permanent Fix: Suggest a concrete resolution with code, configuration, or infrastructure changes. Keep it concise and directly applicable. 5. Prevention & Guardrails: Recommend tests, monitoring alerts, or architectural changes to prevent recurrence. CONSTRAINTS: - Use only the information provided in the log and context. Do not invent error codes, library versions, infrastructure details, or external references. - If critical information is missing or ambiguous, list it in a brief "Open Questions" section instead of guessing. - Format the output as a clean Markdown report using the structure below. - Prioritize production-safe, actionable recommendations. CONTEXT INPUTS: Technology Stack: Technology Stack Environment: Environment Context LOG: ``` Error Log or Stack Trace ``` OUTPUT STRUCTURE: ### 🔍 Root Cause Hypothesis - [Explanation + quoted evidence] ### 🌍 Blast Radius - [Impact analysis] ### 🛑 Immediate Mitigation - [Steps to stop bleeding] ### 🛠️ Permanent Fix - [Code/config sketch] ### 🛡️ Prevention & Guardrails - [Tests/alerts/architecture] ### ❓ Open Questions (if applicable) - [Missing/ambiguous details]

How to use this prompt

  1. Fill in the fields above. Required ones are marked with *.
  2. Check the prompt preview: your answers appear highlighted in place.
  3. Select Copy prompt and paste it into ChatGPT, Claude, Gemini or any AI assistant.

More Software Development & Coding prompts

See all Software Development & Coding prompts