Full Changelog: https://github.com/dash0hq/dash0-operator/compare/0.137.0...0.138.0
Full Changelog: https://github.com/dash0hq/dash0-operator/compare/0.136.0...0.137.0
spam-filters: Add spam-filters command with list, get, create, update, and delete subcommands (#132)
Manage dataset-scoped spam filters via dash0 spam-filters <subcommand>.
Supports file-based input (-f), dry-run validation, and all standard output formats (table, wide, json, yaml, csv).recording-rules: Fix recording rules create and update not passing the dataset as a query parameter (#130)
The --dataset flag and profile dataset were silently ignored for recording-rules create and recording-rules update.
Updated dash0-api-client-go to v1.11.1 which passes the dataset as a query parameter.recording-rules: Add recording rules commands (create, list, get, update, delete) for managing Prometheus recording rules via the PrometheusRule CRD format. (#126)config: Add --profile global flag and DASH0_PROFILE environment variable to select a profile per invocation. (#127)
The selector overrides the active profile on disk for the current invocation
without modifying ~/.dash0/. Precedence is --profile flag → DASH0_PROFILE
→ the active profile. A non-existent profile fails before any API call with a
message listing the available profiles. Passing an empty value falls through
to the next step. config show annotates the Profile: line with the source
when a selector is in effect.Full Changelog: https://github.com/dash0hq/dash0-operator/compare/0.135.0...0.136.0
Google Cloud infrastructure monitoring is now in Dash0. Cloud Run, Pub/Sub, and Cloud Storage metrics flow the moment you connect a project — no setup required.
Zero-configuration metric collection: Connect a GCP project through a guided OAuth flow and Dash0 immediately starts collecting a default metric set across every discovered resource.
Cloud Run monitoring: Instant visibility into Cloud Run Services and Cloud Run Jobs. Track request counts, latency, error rates, CPU, memory, and instance counts.
Pub/Sub monitoring: Topics and subscriptions in a clean nested view. Catch message throughput issues, delivery latency spikes, undelivered message counts, and oldest unacked message age.
Cloud Storage monitoring: Request counts, data transfer volumes, and error rates at the bucket level.
Metric coverage: Each service ships with Core, Default, and Extended metrics tiers. Available in early access: Google Cloud Run Services, Google Cloud Run Jobs, Pub/Sub, Cloud Storage.
Notification channels and routing rules can now be managed as Infrastructure as Code in Dash0. Supports Slack, PagerDuty, email, webhooks, and 17 total integrations.
Dash0 CLI (since v1.9.0): dash0 -X notification-channels create/list/get/update/delete
Terraform provider (since v1.8.0): dash0_notification_channel resource with notification_channel_yaml field.
Kubernetes operator (since v0.136.0): Dash0NotificationChannel CRD that syncs channels to Dash0 and reports status back on the custom resource.
Channels are organization-level resources and can be version-controlled, reviewed in PRs, and replicated across organizations via CI/CD or GitOps workflows.
Full Changelog: https://github.com/dash0hq/dash0-operator/compare/0.134.1...0.135.0
api: Add experimental api command for raw HTTP calls to the Dash0 API. (#122)
The dash0 -X api command performs a raw HTTP request against any Dash0 API endpoint,
reusing the active profile's API URL, auth token, and (by default) dataset.
It is useful for endpoints that do not yet have a dedicated subcommand.metrics: Rework metrics instant with new flags and output formats (#45)
Add --promql flag (replacing the deprecated --query), --filter for PromQL label matcher generation,
--from (replacing the deprecated --time), -o csv output format, --skip-header, and --column for
columnar table and CSV output. The timestamp and value columns are always included automatically.
Deprecated flags (--query, --time) remain functional for backwards compatibility.logs, spans, traces: Promote logs query, spans query, spans send, and traces get commands to stable (#124)
These commands no longer require the --experimental (-X) flag.Dash0 SQL is now generally available. Write queries directly against your logs, spans, and web events.
Full SQL Support: Joins, subqueries, aggregations, and functions for aggregation, string manipulation, date, array, math, logic, JSON extraction, and type conversion. Compatible with AI tools for query generation.
Built-in Query Templates: A library of ready-to-run query examples to start from.
Recent Queries: Local history of your last 20 queries.
Saved Views with Sharing: Save named views that persist across sessions and devices, shareable with teammates.
notification-channels: Add notification-channels command for managing notification channels (list, get, create, update, delete) (#119)
Notification channels are organization-level resources (no --dataset flag).
The command uses CRD-enveloped NotificationChannelDefinition types with file-based input.
All subcommands are experimental and require the -X flag.Drag-to-resize handles have been added to table columns across Dash0's explorers (Trace Explorer, Log Explorer, Web Events Explorer, and Resources). Hover over the table header row to reveal grip handles at column edges, then drag to adjust width. Save your view to persist column sizes across sessions. Use the view reset button or the "Reset column sizes" option in the table Settings menu to revert.
The page.url.domain attribute is now surfaced in three places for multi-site web integrations:
Also: session detail header items now wrap gracefully on smaller screens instead of getting squeezed.
Dash0's MCP server now supports OAuth 2.0 authentication. Tools like Claude Code, Cursor, Windsurf, and other MCP-compatible clients can authenticate without managing static API tokens.
How it works: When you add Dash0 as an MCP server, the tool opens a browser for login and consent. Dash0 handles dynamic client registration, token exchange, and automatic refresh.
Key benefits:
Once connected, AI tools have access to 20+ MCP tools for querying observability data — service catalogs, PromQL metrics, logs, traces, synthetic checks, dashboards, and more.
Bearer token authentication remains fully supported alongside OAuth.
Full Changelog: https://github.com/dash0hq/dash0-operator/compare/0.134.0...0.134.1
Please do not update to 0.134.0 in Google GKE Autopilot clusters. This release is is not compatible with the current workload allowlist for the Dash0 operator. A fix will be released soon.
Full Changelog: https://github.com/dash0hq/dash0-operator/compare/0.133.0...0.134.0