OpenBao

Auto-Detection

Built-in Metrics

OpenBao is an open-source fork of HashiCorp Vault for secrets management. Its metrics are exposed through the same telemetry subsystem as Vault. If you run HashiCorp Vault instead, see the Vault page.

Auto-Detection

Glouton detects OpenBao by its process and listening port (default: 8200).

First, enable the Prometheus telemetry in your OpenBao configuration file (HCL format):

telemetry {
  prometheus_retention_time = "30s"
  disable_hostname = true
}

Restart OpenBao for the change to take effect. The metrics endpoint (/v1/sys/metrics) requires authentication, so you must provide a token that is allowed to read sys/metrics. Set it through the service configuration:

Linux
Windows

sudo tee /etc/glouton/conf.d/99-openbao.conf > /dev/null << 'EOF'
service:
  - type: "openbao"
    address: "127.0.0.1"
    port: 8200
    password: "<YOUR_OPENBAO_TOKEN>"
EOF

Create or edit C:\ProgramData\glouton\conf.d\99-openbao.conf:

service:
  - type: "openbao"
    address: "127.0.0.1"
    port: 8200
    password: "<YOUR_OPENBAO_TOKEN>"

To scrape a non-standard endpoint (for example when OpenBao is served over HTTPS or behind a different path), set stats_url to the full metrics URL instead of address and port.

Glouton automatically detects configuration changes.

Built-in Metrics

Metric	Description
`service_status`	Status of OpenBao
`bao_core_unsealed`	Whether the OpenBao node is unsealed (1) or sealed (0)
`bao_core_active`	Whether the OpenBao node is the active node in the cluster
`bao_core_in_flight_requests`	Number of requests currently being processed
`bao_core_handle_requests`	Rate of requests handled by the core
`bao_core_handle_login_requests`	Rate of login requests handled by the core
`bao_core_check_tokens`	Rate of token checks performed by the core
`bao_core_leadership_losses`	Number of times this node lost cluster leadership
`bao_expire_num_leases`	Number of currently active leases