HashiCorp Consul Autopilot Raft Quorum and Cluster Health Sentinel
Audits HashiCorp Consul Autopilot for Raft quorum health and voter commit index synchronization to prevent cluster brain-split.
Triage a RabbitMQ parking lot or DLQ with Kestra. Each message is logged to Postgres and waits for a person to replay it, fixed if needed, or discard it.
Parking lots and dead-letter queues fill up quietly. When someone finally looks, the usual tools move everything back at once, poison messages included, and nothing records what was replayed or why. This flow turns each parked message into a Kestra execution that records it in a Postgres ledger and pauses. Whoever is on call opens it, reads why it was parked, and resumes it with REPLAY (optionally with a corrected payload) or DISCARD and a note. The message goes back to the work queue or is dropped, and the ledger keeps the decision.
It works with any parking lot or DLQ, and is built to follow rabbitmq-retry-ladder-consumer, which parks messages with the reason and the number of attempts.
This blueprint was created by kruxarth.
on_parked_message (io.kestra.plugin.amqp.RealtimeTrigger) starts one execution per message on orders.parking-lot. Executions run side by side, so a message waiting for a decision never holds up the next one.ensure_ledger creates the parked_messages table on first use.read_parked_message reads the envelope written by the consumer flow (AMQP type kestra.parked-message). Any other message, such as one RabbitMQ dead-lettered itself, is wrapped the same way, with the source queue and reason taken from its x-first-death-* headers.record_parked (io.kestra.plugin.jdbc.postgresql.Query) inserts a PENDING row with bound parameters, and show_parked_message logs the message id, the reason and the payload.await_decision (Pause) waits with three onResume inputs: decision (REPLAY or DISCARD), patched_payload and note.apply_decision (Switch):replay (io.kestra.plugin.amqp.Publish) sends the corrected payload, or the original one, back to orders.work as a persistent message with the same message_id, and the row becomes REPLAYED.DISCARDED.messageId and decision (pending, replay or discard) on every execution.decision: pending, and PENDING rows you can query or chart.Pause with typed onResume inputs gives you an approval form in the UI and an API endpoint, with no extra app to build.RabbitMQ with a parking-lot queue. Running the consumer flow once creates orders.parking-lot; otherwise set parking_lot_queue to your DLQ.
Postgres, reachable from Kestra:
docker run -d --name ledger -p 5432:5432 -e POSTGRES_USER=kestra -e POSTGRES_PASSWORD=change-me -e POSTGRES_DB=messaging postgres:16-alpine
The variables point at localhost. If Kestra runs in Docker, use host.docker.internal instead.
RABBITMQ_USERNAME and RABBITMQ_PASSWORD: a RabbitMQ user that can read the parking lot and write to replay_queue.LEDGER_DB_USERNAME and LEDGER_DB_PASSWORD: a Postgres user that can create the parked_messages table and insert and update its rows.parking_lot_queue at an existing queue).{"order_id": "7"} to orders.parking-lot with the property message_id = order-7.{"order_id": "7", "amount": 10} as the corrected payload, and add a note.SELECT message_id, status, replayed_payload, decision_note FROM parked_messages;orders.parking-lot looks empty while decisions are pending. The paused executions and the PENDING rows hold the messages; don't delete a paused execution before deciding.pauseDuration and behavior on await_decision to discard or escalate automatically.replay_queue through the default exchange, and the consumer flow starts a fresh retry ladder for it.POST /api/v1/<tenant>/executions/<id>/actions/resume with the form fields decision, patched_payload and note.onPause on await_decision, with a link to the execution.PENDING rows grouped by reason.REPLAY_LATER choice that republishes to one of the consumer's delay queues instead.