StructuredFor DevelopersDevOps & CI/CD

Log Analysis & Debugging Guide.

After a production incident when logs are available but the cause is unclear.

ChatGPT Β· Claude Β· GeminiΒ·IntermediateΒ·~900 tokens
Curated by the AIPP team
Last updated 14 May 2026 Β· v3
log-analysis-debugging-guide-4.md Β· 900 words
You are a senior {{role}} brought in to help a developer or tech professional complete a {{use_case}} task.

# Context
- Pack: Developers & Tech Professionals
- Category: DevOps & CI/CD
- Use case: Log Analysis & Debugging Guide
- Source task:
  - I have the following logs from a production issue: {{logs}}. The symptoms are: {{describe_what_users_experienced}}. Help me:
  - 1. identify the root cause from the log evidence
  - 2. construct the timeline of what happened and in what order
  - 3. identify any gaps in logging that made diagnosis harder
  - 4. write improved logging statements to add to prevent this diagnostic difficulty in future
  - 5. recommend log-level and structured logging improvements for the affected code paths

# Goal
Root cause from log evidence, timeline reconstruction, logging gap identification, improved logging code, and structured logging recommendations.

# Constraints
- Produce a complete, usable first draft in one response.
- Avoid generic filler, vague advice, and unsupported claims.
- Make the output specific, practical, and ready to use.

# Output
Root cause from log evidence, timeline reconstruction, logging gap identification, improved logging code, and structured logging recommendations.

The variables to fill in

PlaceholderWhat to put thereExample
{{role}}Roledebugging expert using logs
{{use_case}}Your specific valuelog analysis & debugging guide
{{logs}}LogsExample logs
{{describe_what_users_experienced}}Describe what users experiencedExample describe what users experienced

How to customize this prompt

  1. Replace each {{double-curly}} with your real context.
  2. Adjust the constraints section to match your tone β€” formal, casual, blunt.
  3. If the engagement is recurring, change the duration line to mention milestones rather than days.
  4. Run it in your tool of choice. The output should be ready to paste with at most one small edit.

When to use

After a production incident when logs are available but the cause is unclear.

PRO TIP

Add a correlation ID (request ID) to every log entry β€” without it, you cannot trace a single request across multiple services or log lines.

Related prompts

Structured

Blog Post Drafting Engine

Write a complete, SEO-optimised blog post on the given topic. Include a compelling headline, an engaging introduction, 4-5 subheadings with detailed body paragraphs, and a strong conclusion with a cal

Structured

Email Newsletter Writer

Write a complete email newsletter including subject line, preview text, opening hook, main body content (3 short sections), and a clear call to action.

Structured

YouTube Video Script Writer

Write a complete YouTube video script including a strong hook (first 30 seconds), structured main content with transitions, and a closing that encourages likes, comments, and subscriptions.

Structured

LinkedIn Article Builder

Write a complete LinkedIn article that establishes professional authority, shares a genuine insight, and encourages professional discussion.

β˜… THIS PROMPT IS IN A PACK

The Developer Toolkit Pack

250 technical prompts for code review, documentation, architecture planning, debugging, test writing, API design, and career growth β€” built by developers for developers.

Browse more prompts β†’