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.

Incident Remediation (REQ-108): EventOre eliminates custom redrive scripts and manual database updates by providing an interactive DLQ management suite with single-message replay, bulk redrive, and audit tracking.

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

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
}