OpenBao ObservabilitySearch GitHub

Browse

In This Section

OpenBao metrics scrape failing Use this runbook when the OpenBaoUnreachable alert fires because Prometheus cannot scrape one or more OpenBao metrics targets. The steps help you separate an OpenBao health problem … OpenBao sealed unexpectedly Use this runbook when the OpenBaoSealedUnexpectedly alert fires because a scraped OpenBao node reports core_unsealed as 0. The steps help you confirm whether the seal is planned, … No active OpenBao leader Use this runbook when the OpenBaoNoActiveNode alert fires because Prometheus does not see an active OpenBao node. The steps help you determine whether the cluster has no leader, … Multiple active OpenBao nodes Use this runbook when the OpenBaoMultipleActiveNodes alert fires because Prometheus sees more than one active OpenBao node. Treat this as a possible split-brain incident until you … OpenBao Raft and Autopilot health Use this runbook when a Raft or Autopilot critical alert fires for an OpenBao cluster that uses integrated storage. The steps help you identify whether the cluster lost a peer, … Audit request and response failures Use this runbook when an audit failure alert fires because OpenBao reports request or response audit logging failures. Treat the alert as both an availability risk and an evidence … Audit canary missing Use this runbook when the OpenBaoAuditCanaryMissing alert fires because Loki has not received the expected audit canary request. The canary proves that OpenBao writes audit events, … Audit log stream missing Use this runbook when the OpenBaoAuditStreamMissing warning fires because Loki has not received the openbao.audit stream for the alert window. The steps help you determine whether … Audit archive degraded Use this runbook when the OpenBaoAuditArchiveDegraded alert fires because the durable audit archive path is enabled but missing, stale, failing, or dead-lettering records. The … Operational log stream missing Use this runbook when the OpenBaoOperationalLogStreamMissing alert fires because Loki has not received the openbao.operational stream for the alert window. The steps help you … Debug logging enabled Use this runbook when the OpenBaoDebugTraceLoggingEnabled alert fires because OpenBao operational logs include debug or trace entries. Debug and trace logs can increase log cost … Completed request logging enabled Use this runbook when the OpenBaoCompletedRequestLoggingObserved alert fires because Loki has received OpenBao completed request logs. Completed request logging is a temporary … Irrevocable leases present Use this runbook when the OpenBaoIrrevocableLeasesPresent alert fires because OpenBao reports one or more leases that it cannot automatically revoke. Treat this as a revocation and … Runtime and storage warnings Use this runbook when a runtime or storage warning fires for OpenBao. These alerts point to storage barrier, cache, runtime memory, or mount table changes that need correlation … Secret engine feature warnings Use this runbook when a PKI, Transit, or database secrets engine warning fires for OpenBao. These alerts point to failed or unusually slow feature-specific operations and need … Kubernetes platform health Use this runbook when a Kubernetes platform alert fires for an OpenBao workload. These alerts point to pod readiness, restarts, node pressure, PVC pressure, or collector scrape … SLO and availability Use this runbook when an OpenBao synthetic probe, availability burn-rate, or synthetic latency alert fires. These alerts point to user-facing availability or latency symptoms from … Security audit detections Use this runbook when a security detection alert fires from OpenBao audit logs or completed request logs. These alerts identify sensitive activity that needs change validation and …