About Managing as Code

Dash0 assets can be managed as infrastructure as code, allowing you to version control configurations, automate deployments, and maintain consistency across environments. This approach enables code review for asset changes and collaborative development of observability configurations.

Supported Assets

Dash0 supports infrastructure as code for the following asset types:

• Check Rules — Define alert rules based on metrics, logs, or traces.
• Dashboards — Create visualizations and monitoring panels.
• Notification Channels — Configure alerting destinations (Slack, PagerDuty, email, webhooks).
• Spam Filters — Filter unwanted telemetry data to reduce costs.
• Synthetic Checks — Define uptime and API monitoring checks.
• Views — Save reusable queries and filters for telemetry data.

Each asset type has its own schema and configuration format. All can be exported from the Dash0 UI as YAML and managed through code.

Available Tools

Dash0 provides three infrastructure as code tools for managing assets.

All tools support creating, updating, and deleting assets. Choose based on your existing infrastructure patterns: Kubernetes Operator for Kubernetes-native environments, Terraform for multi-cloud infrastructure, or CLI for scripting and automation.

Benefits of Infrastructure as Code

Managing assets as code provides several advantages:

• Version control — Track changes to configurations in Git, enabling rollback and audit trails.
• Code review — Review changes through pull requests before deployment.
• Consistency — Ensure the same configurations across development, staging, and production environments.
• Automation — Deploy assets through CI/CD pipelines alongside application code.
• Collaboration — Share configurations across teams using standard development workflows.
• Documentation — Asset definitions serve as living documentation of observability configurations.

Workflow

The typical workflow for managing assets as code:

1. Create or export — Build assets in the Dash0 UI and export them as YAML, or write definitions directly.
2. Store in version control — Commit YAML files to your Git repository alongside application code.
3. Review changes — Use pull requests to review modifications to asset definitions.
4. Deploy — Apply changes through your chosen tool (Kubernetes Operator, Terraform, or CLI).
5. Sync — The tool creates or updates assets in Dash0 to match your code.

Further Reading

• Infrastructure as Code: Learn about managing all Dash0 assets as code.
• Manage Check Rules as Code: Define and version check rules through configuration files.
• Manage Dashboards as Code: Define and version dashboards through configuration files.
• Manage Notification Channels as Code: Define and version notification channels through configuration files.
• Manage Spam Filters as Code: Define and version spam filters through configuration files.
• Manage Synthetic Checks as Code: Define and version synthetic checks through configuration files.
• Manage Views as Code: Define and version views through configuration files.