v1.7.0

Enhancements

• output: The update and apply commands now show a unified diff of changes (#66)
• dashboards: <asset> list -o yaml and -o json now output full asset definitions instead of summary list items (#67)
  YAML output is a multi-document stream (separated by ---) that can be piped directly to dash0 apply -f -.
  JSON output is an array of full asset definitions.
  This applies to all four asset types: dashboards, check-rules, views, and synthetic-checks.

v1.6.0

Enhancements

• dashboards: Accept PersesDashboard CRD files in apply and dashboards create (#85)
  PersesDashboard CRDs (perses.dev/v1alpha1 and perses.dev/v1alpha2) are now accepted as input.

v1.5.4

Enhancements

• logs, spans, traces: Add explorer deep link URL as the first line of output for logs query, spans query, and traces get (#71)
  The URL is printed after the table output and links to the corresponding Dash0 explorer view.

v1.5.3

Bug Fixes

• synthetic-checks, views: Display the human-readable name instead of the CRD name for synthetic checks and views (#80)
  The get, create, and update commands for synthetic checks and views now read from
  spec.display.name instead of metadata.name, consistent with dashboards.

v1.5.2

Enhancements

• errors: Include API response body in error messages when the backend does not return a structured error (#75)
  Previously, errors like 400 Bad Request only showed the HTTP status code and trace ID.
  Now, the full response body is displayed so that users can see the reason for the failure.
• dashboards: Make the <id> argument of dash0 <asset> update optional (#76)
  When the <id> argument is omitted, the ID is extracted from the file content.
  This applies to all asset types: dashboards, check rules, synthetic checks, and views.

Bug Fixes

• dashboards: Fix dashboards update overwriting dash0Extensions.id with the origin string (#77)
  Unify ID and name extraction between apply and per-asset CRUD commands by
  delegating to shared Extract* functions in internal/asset/.
• dashboards: Stop force-setting origin in asset update commands (#78)
  The synthetic-checks update, views update, and check-rules update commands
  were force-setting the origin to "dash0-cli", causing 400 errors when updating
  assets originally created with a different origin.

v1.5.1

Bug Fixes

• views: Fix view deeplink URLs to use the correct path for each view type (#72)
  Previously, all view deeplinks used /goto/logs regardless of view type.
  Now each view type maps to its correct deeplink path (e.g., /goto/traces/explorer for span views, /goto/metrics/explorer for metric views).
  The views list output also includes a new TYPE column.

v1.5.0

New Components

• teams: Add experimental team and member management commands (#47)
  New teams commands: list, get, create, update, delete, add-members, remove-members.
  New members commands: list, invite, remove.
  All commands require the --experimental (-X) flag.

Enhancements

• assets: Add CSV output format to asset list commands (#62)
  The dashboards list, check-rules list, views list, and synthetic-checks list commands now accept -o csv.
  CSV output includes all columns from the wide format (name, id, dataset, origin, url).
• query: --column flag for logs query, spans query, and traces get to customize displayed columns (#56)
  Users can now select which columns appear in table and CSV output using repeatable --column flags.
  Predefined columns have short aliases (e.g., time, severity, body for logs).
  Any OTLP attribute key can be used as a column, enabling ad-hoc display of arbitrary attributes.

v1.4.0

New Components

• spans: Add spans query command to query spans from Dash0 (#51)
  Supports table, CSV, and OTLP JSON output formats with filtering, time range selection, and pagination.
• spans: Add spans send command to send spans to Dash0 via OTLP (#51)
  Supports span kind, status, duration, trace/span ID (auto-generated or explicit), parent span, span links, resource/span/scope attributes, and custom instrumentation scope.
• traces: Add traces get command to retrieve all spans in a trace from Dash0 (#51)
  Displays spans in table, JSON (OTLP/JSON), or CSV format.
  Table output shows timestamp, duration, trace ID, span ID, parent ID, span name, status, service name, and span links. Supports --follow-span-links to recursively fetch traces linked through span links.

Enhancements

• logs: Color-code severity levels in logs query table output (#46)
  Severity levels (FATAL, ERROR, WARN, DEBUG, TRACE) are now color-coded when output is a terminal.
  A new global --color flag (env: DASH0_COLOR) controls color output: semantic (default) or none.
• output: Add --skip-header flag to suppress the header row in tabular output formats (#50)
  Available on all asset list commands (table and wide formats), config profiles list and logs query (table and CSV formats).

v1.3.0

Enhancements

• logs: Add dash0 logs query command to query log records from Dash0 (#41)
  The command syntax — especially the --filter format — is experimental and may change in future releases.

v1.2.0

New Components

• github-actions: send-log-event GitHub Action to send log events to Dash0 directly from your GitHub workflows. (#40)
  The action is standalone and installs the Dash0 CLI automatically.
  If the setup action has already run, the existing installation is reused.

Enhancements

• assets: Add deeplink URLs to get and list -o wide output for all asset types (#36)
  The get command now shows a URL field linking directly to the asset in the Dash0 web UI.
  The list -o wide command includes a URL column with deeplink URLs for each asset.