skip to content

--:--:--·05

projects github

~/projects/dlqautopsy

dlqautopsy

’26 · go · cli · sqlite

open source

g go esc index

dlqautopsy · classify prod-incidenttty

[CRIT] Poison Message           DO NOT RETRY[WARN] Downstream Dependency    SAFE TO RETRY[WARN] Transient Error          RETRY WITH BACKOFF

inspect · classify · report · detail

Reads DLQ payloads on your machine and groups them by failure signature.

A dead letter queue tells you something failed. It does not tell you why, whether two thousand messages are the same bug, or which ones are safe to retry.

dlqautopsy pulls payloads onto your machine, into SQLite (autopsy.db). inspect reads the queue. classify maps errors to classes: poison, downstream, transient, auth, config, network, resource. report prints triage. detail opens one class. diff compares two runs. runs lists what is in the file. There is no model guessing.

It does not redrive messages. Use the cloud API for that. It does not alert. It does not upload your payloads.

example

With AWS creds in your env, go run scripts/seed_sqs.go creates a test queue and DLQ, sends about 200 messages, and exhausts retries so they land in the DLQ. It prints: dlqautopsy inspect --name prod-incident --queue-url <that-url> Then classify --name prod-incident and report --name prod-incident. Verdicts are DO NOT RETRY and SAFE TO RETRY. It does not redrive.

github.com/doganaydindev/dlqautopsy ↗

prevferris-pulse nextk8s logs

mail dogan@hey.com source github.com/doganaydindev

retconferris-pulsedlqautopsyk8s logsnmap-tui