boundary-obs

Register Prometheus targets and Grafana dashboards for Boundary monitoring in HAL's OBS stack.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Boundary observability artifacts can become scattered across manual configurations, leading to inconsistent monitoring data.

Core Features & Use Cases

  • Register Prometheus targets for Boundary monitoring and import the Grafana dashboard into the HAL OBS stack.
  • Update or re-register artifacts to ensure idempotent configuration across restarts and environment changes.
  • Provide status visibility for Boundary monitoring artifacts within the shared observability stack.

Quick Start

Run hal boundary obs create to register the Prometheus target and import the Boundary Grafana dashboard when the obs stack is running.

Frequently Asked Questions about boundary-obs

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

FAQPage Schema
How do I wire Boundary metrics into Prometheus and Grafana?

To register Boundary monitoring artifacts, ensure the OBS stack is running, then execute `hal boundary obs create` to register the Prometheus target and import the Boundary Grafana dashboard automatically.

What is the process for onboarding Boundary monitoring into a shared observability stack?

Onboarding Boundary monitoring involves orchestrating the registration of Prometheus targets and Grafana dashboards into the shared OBS stack using idempotent operations via `hal boundary obs` commands.

Do I need a running observability stack to register Boundary monitoring artifacts?

Yes, you need the OBS stack running to register Boundary monitoring artifacts. The process requires the Boundary controller endpoint, Prometheus, and Grafana to be accessible at their respective localhost URLs.

Can I update or check the status of Boundary monitoring artifacts after initial onboarding?

Yes, you can update or check the status of Boundary monitoring artifacts using the `hal boundary obs update` and `hal boundary obs status` commands, which support idempotent configuration across restarts and environment changes.

Why does re-registering Boundary observability artifacts not break my existing dashboard configuration?

Re-registering Boundary observability artifacts does not break existing dashboard configuration because the `hal boundary obs` commands perform idempotent operations, ensuring consistent configuration across restarts and environment updates.