Skip to content
Provider · Observability

Datadog — Ashlr Stack Provider

Datadog: Metrics, traces, logs. API + Application keys verified via /api/v1/validate. Wire it into your project with one command via Ashlr Stack.

Observability · API key KEY-ONLY · v0.2 adds provisioning
Datadog — Metrics, traces, logs. API + Application keys verified via /api/v1/validate.
Dashboard ↗

One command

Add Datadog 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 datadog

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 long-lived API key once. Stack verifies it against the provider's API before writing to Phantom.

How-to: Create an API key at https://app.datadoghq.com/organization-settings/api-keys and an Application key at https://app.datadoghq.com/organization-settings/application-keys.

Secret slots

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

  • DD_API_KEY
  • DD_APP_KEY

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.

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

FAQ

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

Yes — Stack provisions Datadog on your behalf, but it authenticates as you. Paste a long-lived API key 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://app.datadoghq.com and paste it once.

Where does Stack store my Datadog credentials?

In Phantom Secrets, an E2E-encrypted local vault. Stack writes the secret slot names (DD_API_KEY, DD_APP_KEY) 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 datadog` to pull the Datadog service back out (Phantom secrets deleted, MCP entry removed, .stack.toml cleaned up). Rotate the underlying Datadog credentials in their dashboard — https://app.datadoghq.com — and Stack's next `doctor --fix` will pick up the new values.

Outbound