HashiCorp Vault check
vault — HashiCorp Vault
Seal status (sealed or uninitialized), active/standby role, and the running version.
checkfleet check vault --config checkfleet.yml
Checks a Vault node over its HTTP API (zero-dep):
- Seal status (
/v1/sys/seal-status) —ERRORif unreachable,BADif the node is sealed (with unseal progressn/threshold) or not initialized. - Role (
/v1/sys/health) — reportsactiveorstandby(bothOK— standby is normal in an HA cluster) with the Vault version.
Both endpoints are unauthenticated; an optional token_env sends X-Vault-Token
for setups that restrict them. insecure_skip_verify for self-signed HTTPS.
Tested against an in-test fake Vault.
vault:
targets:
- {name: vault-01, url: https://vault-01:8200}
See the full module reference for every check, or configuration for the config keys.