About the Dash0 Terraform Provider

The Dash0 Terraform Provider manages Dash0 observability assets — dashboards, alerting rules, saved views, synthetic checks, notification channels, spam filters, and teams — 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_dashboardCopy — Perses dashboards.
• dash0_check_ruleCopy — Prometheus-style alerting rules.
• dash0_recording_ruleCopy — Prometheus recording rule groups.
• dash0_viewCopy — saved telemetry queries.
• dash0_synthetic_checkCopy — HTTP-based availability probes.
• dash0_notification_channelCopy — Slack, email, PagerDuty, Opsgenie, webhook, Microsoft Teams, Discord, and Google Chat destinations.
• dash0_spam_filterCopy — ingestion-time telemetry filters.
• dash0_teamCopy — organization-level teams that group members and own assets.

Actions

Not everything worth doing from Terraform is an asset to reconcile. Actions are point-in-time operations that hold no state, run only when invoked, and are available from Terraform 1.14 onward.

The following actions allow you to send telemetry to Dash0 about changes you enact via Terraform:

• dash0_deployment_eventCopy — emits a dash0.deploymentCopy event marking when a service was deployed, so the deployment can be overlaid on charts as a dashboard annotation.
• dash0_log_eventCopy — sends an arbitrary log event via OTLP, mirroring the dash0 logs sendCopy CLI command.

Both require the otlp_urlCopy provider attribute, which addresses the Dash0 OTLP ingress endpoint rather than the API. Attach an action to a resource with a lifecycleCopy action_triggerCopy block, or invoke it on its own with terraform apply -invokeCopy:

1234567891011121314151617181920
action "dash0_deployment_event" "release" {
  config {
    service_name                = "checkout-api"
    service_version             = var.image_tag
    deployment_environment_name = "production"
    deployment_status           = "succeeded"
    dataset                     = "production"
  }
}

resource "kubernetes_deployment" "checkout_api" {
  # ... deployment configuration ...

  lifecycle {
    action_trigger {
      events  = [after_create, after_update]
      actions = [action.dash0_deployment_event.release]
    }
  }
}

See dash0_deployment_eventCopy and dash0_log_eventCopy for the full schema, more action_triggerCopy patterns, and the required provider setup.

Authentication

The provider accepts credentials from three sources, checked in order:

1. Environment variables (DASH0_API_URLCopy, DASH0_AUTH_TOKENCopy).
2. Provider-block attributes (urlCopy, auth_tokenCopy).
3. A named Dash0 CLI profile — including OAuth-enabled profiles created with dash0 auth loginCopy, which the provider refreshes automatically before every request.

See Configuration for the full providerCopy 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 PersesDashboardCopy, PrometheusRuleCopy, and Dash0-specific custom resources — the right choice for GitOps flows already anchored on kubectl applyCopy and 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_ruleCopy.
• Configuration — the full providerCopy block 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-dash0Copy for issues, changelog, and contributions.