Infrastructure as Code (IaC) enables you to define, version, and deploy Dash0 assets through configuration files rather than manual UI interactions. This approach brings software development practices like code review, automated testing, and CI/CD pipelines to observability configuration, ensuring consistency across environments and enabling collaborative asset development.

Dash0 supports managing multiple asset types as code: dashboards, views, check rules, notification channels, synthetic checks, and spam filters. Each asset can be exported from the Dash0 UI to YAML format, modified in your code editor, stored in version control, and deployed through automated pipelines.

Available Tools

Dash0 provides three complementary IaC tools, each optimized for different workflows:

Dash0 Operator for Kubernetes — Define assets as custom resources (CRDs) that sync automatically to Dash0. The operator watches for changes to resources like Dash0View, PersesDashboard, and PrometheusRule, creating and updating corresponding assets in Dash0. This enables GitOps workflows where configuration changes trigger automated deployments through tools like ArgoCD or Flux.
Dash0 Terraform Provider (on the Terraform and OpenTofu registries) — Manage Dash0 assets in Terraform configurations alongside your cloud infrastructure. Resources like dash0_dashboard, dash0_view, and dash0_check_rule integrate into your existing Terraform workflows, allowing you to provision observability configuration as part of infrastructure deployment. Changes are applied through standard Terraform commands (plan, apply) with state management and drift detection.
Dash0 CLI — Script asset operations for batch deployments, migrations, and automation. The CLI provides commands for creating, updating, listing, and deleting assets across all supported types. This is useful for one-off migrations, bulk operations across multiple assets, and integration into custom deployment scripts or CI/CD pipelines that don't use Kubernetes or Terraform.

All three tools work with the same YAML formats exported from the Dash0 UI. Assets managed as code are marked read-only in the UI to prevent drift between your configuration files and live assets. You can delete or clone IaC-managed assets through the UI, but edits must be made in your configuration files and redeployed.

Benefits and Use Cases

Managing Dash0 assets as code provides several advantages over manual UI configuration:

Version control and audit trails — Every change to dashboards, check rules, or other assets is tracked in Git with commit messages, author information, and the ability to revert to previous versions. This creates a complete audit trail of who changed what and when.
Code review and collaboration — Configuration changes go through pull requests where team members can review, comment, and approve modifications before deployment. This catches errors early and spreads knowledge across the team.
Environment consistency — Use the same configuration files across development, staging, and production environments with parameterization for environment-specific values. This ensures production monitoring mirrors lower environments and reduces environment-specific bugs.
Automated testing and deployment — Integrate asset deployment into CI/CD pipelines with automated validation. Test that check rules trigger correctly, dashboards render properly, and views return expected data before promoting to production.
Disaster recovery — Configuration files in version control serve as backups. If assets are accidentally deleted or misconfigured, you can restore them by redeploying from Git. This reduces mean time to recovery for observability infrastructure.
Batch operations and migrations — Update multiple assets simultaneously through code changes rather than clicking through the UI for each one. This is particularly valuable when migrating to new semantic conventions, renaming services, or standardizing dashboard layouts across teams.

Infrastructure as Code

Available Tools

Benefits and Use Cases

Further Reading