Dead-Letter Queue (DLQ) Inspector & Message Redrive
Isolate poisoned messages, analyze exception stacktraces, repair malformed JSON payloads in-place, and safely redrive records back to production queues.
The Operational Nightmare of DLQs
When consumer microservices encounter unparseable payloads, schema mismatches, or transient third-party API failures, resilient systems route those records to a Dead-Letter Queue (e.g. orders.dlq, payments-deadletter).
Historically, operators had to write one-off Python or Bash scripts to fetch messages from the DLQ, edit the JSON payload to fix a missing attribute, and re-produce to the original topic. This workflow is error-prone and risks corrupting partition order or leaking unmasked PII.
EventOre DLQ Suite Capabilities
- Automatic DLQ Detection: Auto-discovers dead-letter topics and queues matching standard naming conventions (
*.dlq,*.deadletter,*-retry-exhausted) or custom configured regex. - Exception Header Inspection: Decodes and displays error stacktraces typically stored in headers (e.g.,
x-exception-message,x-death,x-exception-stacktrace, or Spring Kafkakafka_dlt-exception-message). - In-Place Payload & Header Editor: Syntax-highlighted JSON editor allows operators to fix typos or missing fields directly in the browser with JSON schema validation.
- Dry-Run Redrive: Simulates destination publishing and schema validation before committing the redrive transaction.
- Target Destination Selection: Redrive back to the original source topic, a designated staging retry topic, or a newly configured target broker.
- Bulk Replay: Republish a bounded batch of sampled messages. Redrive does not remove source messages and does not currently throttle requests; use small batches and verify downstream capacity.
- Audit Logging: Every redrive action records who initiated the replay, timestamp, original vs edited payload diff, and target receipt confirmation.
Redrive REST API
Redrive operations can also be triggered via CI/CD or operational automation:
POST /api/v1/connections/{id}/dlq/redrive
Content-Type: application/json
{
"dlqTopic": "orders.v1.dlq",
"targetTopic": "orders.v1",
"messageIds": ["offset-49281", "offset-49282"],
"payloadOverrides": {
"offset-49281": "{\"orderId\":\"ORD-101\",\"amount\":42.50,\"currency\":\"USD\"}"
},
"injectHeader": {
"X-Redrive-Origin": "EventOre-DLQ-Engine",
"X-Redrive-Operator": "sre-oncall"
},
"rateLimitPerSecond": 100
}