Commands icon
If icon
SlackIncomingWebhook icon
Schedule icon

HashiCorp Consul Raft Leader Stability and Quorum Sentinel

Audits HashiCorp Consul Raft consensus cluster leadership and voter quorum to prevent service discovery outages.

Categories
CloudInfrastructure

How it works

This workflow connects to the HashiCorp Consul HTTP API (/v1/status/leader and /v1/operator/raft/configuration) to audit cluster Raft consensus health. In Consul, service discovery, health check registrations, and KV store operations rely entirely on a stable Raft leader and active voting quorum. When network partitions or unexpected node crashes reduce voter counts below majority threshold, leadership is lost, throwing the cluster into read-only or unreachable states. This sentinel verifies active leader presence, validates minimum voter counts, and dispatches incident alerts before service discovery collapses.

What you get

  • Real-time detection of Consul Raft consensus leadership instability.
  • Early warning before service mesh and microservice routing failures.
  • Automated Slack incident notifications with leader address and voter counts.

Who it's for

  • Infrastructure and Platform Engineers maintaining HashiCorp Consul clusters.
  • SREs safeguarding microservice discovery and service mesh connectivity.
  • DevOps Teams operating distributed multi-datacenter Consul topologies.

Why orchestrate this with Kestra

  • Scheduled Surveillance: Periodically audits consensus health every 10 minutes.
  • Native API Capabilities: Interacts directly with standard REST endpoints without agents.
  • Enterprise Secret Storage: Secures Consul ACL management tokens inside Kestra secrets.

Prerequisites

  • HashiCorp Consul cluster with accessible HTTP API (8500).
  • Slack incoming webhook URL configured in SLACK_WEBHOOK secret.

Quick start

  1. Import this blueprint into your Kestra instance.
  2. Add SLACK_WEBHOOK to your namespace secrets.
  3. Specify consul_addr.
  4. Enable the schedule trigger for continuous consensus monitoring.

How to extend

  • Query /v1/health/state/critical to identify specific failing service nodes.
  • Trigger automated server node replacement via cloud infrastructure APIs.
  • Alert to Microsoft Teams or PagerDuty.

Links

See How

New to Kestra?

Use blueprints to kickstart your first workflows.