SkillVaultskills Browse all 1,000+ skills

Debugging · Version 1.1.0 · Reviewed 2026-08-02

RabbitMQ Production Debug Specialist

Diagnose RabbitMQ production incident triage and RabbitMQ root-cause isolation with evidence, explicit trade-offs, and a verification plan.

4 method steps 6 documented failure modes 5 diagnostic checks 7 quality gates

Diagnoses production failures from runtime evidence instead of symptom matching in RabbitMQ using exchange and queue topology, consumer settings, policies, and retry paths and queue depth, unacked messages, redeliveries, memory alarms, and publish confirms, with explicit attention to requeue loops or unbounded prefetch concentrating work and memory on one consumer.

₹199 one-time

Get this skill archive

Install in your AI coding tool

SkillVault packages this skill in the open Agent Skills format for five leading coding tools.

What this skill helps you do

  • RabbitMQ production incident triage
  • RabbitMQ root-cause isolation
  • RabbitMQ fix verification

How RabbitMQ Production Debug Specialist works

You provide

Topic config, consumer settings, and lag history

It inspects

Per-partition lag and processing time for RabbitMQ production incident triage

It decides

A RabbitMQ root-cause isolation decision with ordering guarantees stated

You verify

Lag flattens and dead-letter volume stays bounded

What it checks first

RabbitMQ Production Debug Specialist diagnoses production failures from runtime evidence instead of symptom matching in RabbitMQ using exchange and queue topology, consumer settings, policies, and retry paths and queue depth, unacked messages, redeliveries, memory alarms, and publish confirms, with explicit attention to requeue loops or unbounded prefetch concentrating work and memory on one consumer. Use it when the work involves RabbitMQ production incident triage, RabbitMQ root-cause isolation, RabbitMQ fix verification.

  1. Consumer lag trend rather than absolute value: flat lag at any level is healthy, rising lag is not.
  2. Partition count versus consumer count, since consumers beyond the partition count are idle by definition.
  3. Whether the partition key produces even distribution, or a few keys dominate one partition.
  4. Rebalance frequency, which converts into repeated processing pauses.
  5. Whether offsets commit before or after processing, which decides between at-most-once and at-least-once.

Failure modes it recognizes

  • A poison message blocking a partition indefinitely because the consumer retries in place without dead-lettering.
  • Processing time exceeding the poll interval, causing the broker to evict the consumer and trigger a rebalance loop.
  • Committing offsets before processing, silently dropping messages on crash.
  • Producer key set to null or a timestamp, destroying ordering guarantees the consumer assumed.
  • Consumer group rebalance storms from short session timeouts on a slow consumer.
  • Unbounded retention plus a compaction misconfiguration filling disk and stopping the broker.

Answers it will reject

  • Adding consumers to reduce lag when partitions are already saturated — throughput is bounded by partitions.
  • Increasing partitions to fix lag without checking whether processing is CPU-bound downstream.
  • Treating the queue as a database by retaining everything and querying it by scan.
  • Requeueing a failed message to the tail forever, converting a bug into an infinite loop.

Decision rules it applies

  • Order is guaranteed only within a partition, so any ordering requirement must map to a partition key.
  • Choose at-least-once with idempotent consumers over attempting exactly-once across systems.
  • Dead-letter after a bounded retry count with the failure reason attached; never retry indefinitely in place.
  • Size partitions for peak throughput plus headroom, because increasing partitions later breaks key-to-partition mapping.

Evidence it asks for

  • Track consumer lag per partition, not aggregated, so a single stuck partition is visible.
  • Measure processing time per message against `max.poll.interval.ms`.
  • Alert on rebalance rate and on dead-letter volume as separate signals.

The method inside

  1. Reconstruct the symptom timeline and define what healthy behavior would look like for RabbitMQ production incident triage.
  2. Rank hypotheses for RabbitMQ root-cause isolation by evidence, blast radius, and ability to explain every observed symptom.
  3. Run the cheapest discriminating check for RabbitMQ fix verification; update confidence only when evidence changes.
  4. Separate immediate stabilization, confirmed cause, contributing conditions, and prevention; finish with a reproducible verification.

Deliverables

  • RabbitMQ production incident triage assessment
  • RabbitMQ root-cause isolation decision and action plan
  • RabbitMQ fix verification verification checklist

Evidence requirements

  • Exact symptoms and timestamps
  • Reproduction conditions and recent changes
  • Logs, traces, metrics, code, or configuration

Quality gates

  • Every material claim traces to supplied evidence or is labeled as a hypothesis.
  • The response follows the declared deliverable contract.
  • No execution, access, measurement, or verification is invented.
  • Secrets and personal data are redacted rather than repeated.
  • The user receives a concrete independent verification step.
  • The relevant failure modes in this domain were considered rather than only the reported symptom.
  • No listed anti-pattern was recommended as a solution.

Example task

Input

Apply the production debug specialist to our RabbitMQ system before the next production change. We can provide exchange and queue topology, consumer settings, policies, and retry paths; the main concern is requeue loops or unbounded prefetch concentrating work and memory on one consumer.

Expected output

Start with queue depth, unacked messages, redeliveries, memory alarms, and publish confirms and split the affected population before changing configuration. The leading hypothesis is requeue loops or unbounded prefetch concentrating work and memory on one consumer. Run the smallest test that distinguishes that mechanism from dependency failure, preserve the evidence, and verify recovery against the original symptom.

Boundaries and compatibility

Ideal for

  • RabbitMQ production incident triage: produce a decision or artifact grounded in supplied evidence.
  • RabbitMQ root-cause isolation: produce a decision or artifact grounded in supplied evidence.
  • RabbitMQ fix verification: produce a decision or artifact grounded in supplied evidence.

Out of scope

  • Guessing a root cause from a symptom alone
  • Claiming a fix worked without test evidence

Agent compatibility

  • GitHub Copilot Agent Skills
  • Cursor Agent Skills
  • Claude Code Skills
  • OpenAI Codex Skills
  • JetBrains Junie Skills

Tool policy: Advisory by default. No tools are assumed. If the host provides tools, use read-only evidence gathering unless the user explicitly approves a scoped write or execution action.