Manage Dashboards, Views, Check Rules, and Synthetic Checks from the Terminal
Infrastructure as code changed how teams manage servers. The same principle should apply to observability: your dashboards, alerting rules, views, and synthetic checks deserve version control, code review, and automated deployment. The Dash0 CLI gives you full CRUD control over all four asset types, plus the apply command that brings GitOps workflows to your observability configuration.
One consistent interface for every asset type
Dashboards, check rules, views, and synthetic checks all share the same set of subcommands:
dash0 dashboards list
dash0 check-rules get <id>
dash0 views create -f view.yaml
dash0 synthetic-checks update <id> -f check.yaml
dash0 dashboards delete <id>list, get, create, update, delete: the same verbs, the same flags, the same output formats across every asset type. No need to learn a different interface for each one.
Export, edit, re-apply
The get command with -o yaml or -o json gives you the full asset definition, ready for editing:
dash0 dashboards get <id> -o yaml > dashboard.yaml
# edit dashboard.yaml
dash0 dashboards update <id> -f dashboard.yamlThe apply command: GitOps for observability
apply is the single command that ties it all together.Point it at a file or a directory, and it figures out the rest:
# Apply a single file
dash0 apply -f dashboard.yaml
# Apply an entire directory recursively
dash0 apply -f assets/The command auto-detects whether each asset needs to be created or updated. Multi-document YAML files (separated by ---) let you bundle related assets into a single file. Hidden files and directories are skipped, so your .git folder stays out of the way.
Prometheus alerting rules, native in Dash0
Already have Prometheus alerting rules? The CLI accepts PrometheusRule CRD files directly:
dash0 check-rules create -f prometheus-rules.yaml
dash0 apply -f prometheus-rules.yamlEach alerting rule in the CRD becomes a Dash0 check rule. Recording rules are skipped automatically. No manual conversion required.
Multiple output formats
Every list and get command supports table, wide, json, yaml, and csv output. Use wide for a quick overview that includes dataset, origin, and URL. Use csv with --skip-header for machine-readable automation.
Get started
export DASH0_API_URL=... # Get the value at https://app.dash0.com/goto/settings/endpoints?endpoint_type=api_http
export DASH0_AUTH_TOKEN=... # Get the value at https://app.dash0.com/goto/settings/auth-tokens
# See what you have
dash0 dashboards list
# Export, tweak, and re-apply
dash0 dashboards get <id> -o yaml > my-dashboard.yaml
dash0 apply -f my-dashboard.yamlAsset management is available in all stable releases of the Dash0 CLI: no experimental flag needed.