Provider · Observability

Grafana — Ashlr Stack Provider

Grafana: Dashboards + alerting. Service-account token verified against your Grafana instance. Wire it into your project with one command via Ashlr Stack.

Observability · PAT KEY-ONLY · v0.2 adds provisioning

Grafana — Dashboards + alerting. Service-account token verified against your Grafana instance.

Dashboard ↗

One command

Add Grafana to any Ashlr Stack project with a single command. Stack runs the auth flow, verifies the credential, and writes every secret slot into Phantom.

stack add grafana

Or describe what you're building and let Claude pick it up via stack recommend:

stack recommend "I need a observability provider"

Auth flow

Paste a personal access token (PAT) once. Stack verifies it against the provider's API before writing to Phantom.

How-to: Create a service-account token in Grafana → Administration → Service accounts, and provide your Grafana base URL.

Secret slots

stack add grafana writes these 2 secret slots into your Phantom vault:

GRAFANA_API_KEY
GRAFANA_URL

The values never leave Phantom in plaintext. Your .env file references slot names, and stack exec -- <cmd> swaps them in at process-spawn time via Phantom's local proxy.

Datadog — Metrics, traces, logs. API + Application keys verified via /api/v1/validate.

FAQ

Do I need a Grafana account to use it with Stack?

Yes — Stack provisions Grafana on your behalf, but it authenticates as you. Paste a personal access token (PAT) once. Stack verifies it against the provider's API before writing to Phantom. If you don't have a credential yet, create one at https://grafana.com and paste it once.

Where does Stack store my Grafana credentials?

In Phantom Secrets, an E2E-encrypted local vault. Stack writes the secret slot names (GRAFANA_API_KEY, GRAFANA_URL) into .stack.toml — the actual values live only in Phantom and never touch disk in plaintext.

Can I rotate or revoke this integration later?

Yes. Run `stack remove grafana` to pull the Grafana service back out (Phantom secrets deleted, MCP entry removed, .stack.toml cleaned up). Rotate the underlying Grafana credentials in their dashboard — https://grafana.com — and Stack's next `doctor --fix` will pick up the new values.