Manages a Dash0 Dashboard. Dashboards provide visualizations of your telemetry data such as metrics, logs, and traces. See About Dashboards for more details. The dashboard definition uses the Perses Dashboard format.

Example Usage

terraform

1234
resource "dash0_dashboard" "my_dashboard" {
  dataset        = "default"
  dashboard_yaml = file("${path.module}/dashboard.yaml")
}

Schema

Required

dashboard_yaml (String) The dashboard definition in YAML format, following the Perses Dashboard specification. The following metadata.annotations are supported: dash0.com/sharing (sharing settings) and dash0.com/folder-path (folder location). Changes to these annotations trigger a resource update; all other metadata annotations are managed by the server and ignored during drift detection.
dataset (String) The identifier of the Dash0 dataset that the dashboard belongs to. Provide the dataset's identifier, which is immutable, not the 'name'. Datasets are used to separate observability data within a Dash0 organization. Changing this value forces the resource to be recreated.

Read-Only

id (String) The server-assigned UUID of the dashboard, resolved by the provider after creation. Reference this value when wiring the dashboard's identifier into another resource (for example, as a check rule annotation that links back to the dashboard).
origin (String) A unique identifier for the dashboard, automatically generated on creation. Used to reference the dashboard for updates, reads, deletes, and imports.
url (String) The URL to open this dashboard in the Dash0 web app, derived from the Dash0 API URL and the dashboard's server-assigned identifier. Computed by the provider after creation. May be empty if the app URL cannot be derived (e.g. for self-hosted deployments with a custom web app domain).

Import

Import is supported using the following syntax:

The terraform import command can be used, for example:

shell

12
#!/bin/bash
terraform import dash0_dashboard.name "{{ dataset }},{{ id_or_origin }}"