vault-obs

Manage Vault observability artifacts with idempotent hal vault obs commands.

29|8|Updated Mar 24, 2026
One-click install
npx skills add https://github.com/hashimiche/hal --skill vault-obs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vault-obs
Source: https://github.com/hashimiche/hal/tree/main/internal/skills/data/vault/obs
Command: npx skills add https://github.com/hashimiche/hal --skill vault-obs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Vault observability artifacts are managed and wired into HAL's observability stack, enabling Prometheus targets and Grafana dashboards for Vault.

Core Features & Use Cases

  • Register Prometheus targets and import the Vault Grafana dashboard into HAL's obs stack.
  • Update registrations and dashboards in an idempotent way when Vault changes.
  • Remove Vault monitoring artifacts cleanly when no longer needed, with status visibility.

Quick Start

Ensure the shared obs stack is running, then run hal vault obs create to onboard Vault metrics and Grafana dashboards.

Frequently Asked Questions about vault-obs

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I monitor Vault metrics with Prometheus and Grafana?

You can wire Vault metrics into Prometheus and Grafana by registering Prometheus targets and importing the Vault Grafana dashboard into your observability stack. This onboarding flow surfaces Vault metrics for monitoring.

What is the best way to update Grafana dashboards after Vault configuration changes?

The best way to update Grafana dashboards after Vault changes is to run an idempotent update command. This re-registers targets and dashboards within the observability stack without duplicating artifacts, ensuring your monitoring reflects recent Vault modifications.

Do I need the observability stack running to onboard Vault monitoring?

Yes, the observability stack must be running before you onboard Vault monitoring. The onboarding flow is explicitly opt-in and requires the shared observability infrastructure to be active so it can successfully register Prometheus targets and Grafana dashboards.

How do I cleanly remove Vault monitoring artifacts when no longer needed?

You can cleanly remove Vault monitoring artifacts by running a delete command. This removes the registered Prometheus targets and Grafana dashboards from the observability stack, ensuring no orphaned monitoring configurations remain after Vault is decommissioned.

How do I check the status of Vault observability registrations?

You can check the status of Vault observability registrations by running a status command. This provides visibility into the current state of your Vault Prometheus targets and Grafana dashboards within the shared observability stack.