Last updated: July 19, 2026
About the Dash0 Terraform Provider
Introduction to the Dash0 Terraform Provider — who it's for, the assets it manages, its design principles, and how it relates to the Dash0 Operator and CLI.
The Dash0 Terraform Provider manages Dash0 observability assets — dashboards, alerting rules, saved views, synthetic checks, and notification channels — as Terraform resources. It is published on the Terraform and OpenTofu registries.
Managed assets
Each Dash0 asset kind is exposed as a Terraform resource whose primary attribute is a YAML document using the same formats exported from the Dash0 UI or the Dash0 CLI.
dash0_dashboard— Perses dashboards.dash0_check_rule— Prometheus-style alerting rules.dash0_recording_rule— Prometheus recording rule groups.dash0_view— saved telemetry queries.dash0_synthetic_check— HTTP-based availability probes.dash0_notification_channel— Slack, email, PagerDuty, Opsgenie, webhook, Microsoft Teams, Discord, and Google Chat destinations.dash0_spam_filter— ingestion-time telemetry filters.
Authentication
The provider accepts credentials from three sources, checked in order:
- Environment variables (
DASH0_API_URL,DASH0_AUTH_TOKEN). - Provider-block attributes (
url,auth_token). - A named Dash0 CLI profile — including OAuth-enabled profiles created with
dash0 auth login, which the provider refreshes automatically before every request.
See Configuration for the full provider block schema, the supported environment variables, and end-to-end examples for each authentication source.
Related tooling
- The Dash0 Operator for Kubernetes manages the same assets as
PersesDashboard,PrometheusRule, and Dash0-specific custom resources — the right choice for GitOps flows already anchored onkubectl applyand ArgoCD or Flux. - The Dash0 CLI scripts the same operations for one-off migrations, batch deployments, or shell-driven automation.
- See About Managing as Code for a side-by-side of when to pick which.
Next steps
- Quickstart — a five-minute walkthrough that declares the provider, authenticates, and applies your first
dash0_check_rule. - Configuration — the full
providerblock schema and environment-variable reference. - Resource reference — the sibling pages under Resources document the schema, example usage, and import syntax of each resource type.
- AWS integration via CloudFormation — deploy the Dash0 AWS integration alongside your Terraform-managed Dash0 assets.
- Provider source —
github.com/dash0hq/terraform-provider-dash0for issues, changelog, and contributions.