Dash0 Release Notes

SignalControl, now in every Dash0 account, filters, samples, and aggregates telemetry before anything is stored, so storage is billed only on what you keep.

Dash0’s Google Cloud integration now lets you filter the resources to monitor and select individual metrics to collect. Coverage also expands to Google Kubernetes Engine, Memorystore for Redis, and Compute Engine VMs.

Dash0 can now send failed checks, synthetic check failures and Agent0 automation notifications straight to Mattermost.

Available Dash0 plugins for Coding Harnesses (Claude Code, Cursor, Codex, GitHub Copilot CLI) are now available for Windows.

Message @dash0 directly to chat with Agent0 in a private thread. Your DMs carry their own organization and dataset, so you can ask about data your teammates do not work in without posting it in a shared channel.

Cardinality is now a metric. dash0.metrics.timeseries reports your distinct series count, so you can chart it, alert on it, and group it by metric name or by any resource attribute.

Every Dash0 alert in Slack now has a Fix this in thread button. One click asks Agent0 to explain the failing check, and the answer lands in the alert's own thread.

The Dash0 CLI now manages the whole lifecycle of your assets with the new, experimental apply --since option, which deletes assets based on Git history.

Dash0 now connects to GitLab, on gitlab.com or a self-managed instance. Agent0 reads the diffs, issues and pipelines behind your telemetry, so an investigation is grounded in the code that actually changed, and it can open a merge request when you ask. It works through your own GitLab account, so it reaches only what you can reach.

Mention @dash0 in a Slack channel to chat with Agent0 in the thread. It investigates alerts, finds your logs, builds dashboards and checks, and opens a PR with the fix.

You can now create deployment events and other log events via the Dash0 Terraform Provider through actions.

Time-series panels can now show your deployments as markers on the timeline, colored by whether the deployment succeeded or failed. Send a dash0.deployment log event from your pipeline and every chart can tell you when the code changed.

Write action approval is a new Agent0 setting that makes Chat stop and ask you before it does anything that writes. Organization admins turn it on in Settings → Agent0.

The Dash0 Operator for Kubernetes v1.151.0 introduces automatic instrumentation support for Ruby 3.3+.

Agent0, Dash0's observability agent, can now be reached from Claude Code, Cursor, or any MCP client. Rather than your assistant running one query at a time, ask "why did checkout get slow at 14:00" and Agent0 investigates across your metrics, logs, traces, and profiles, then tells you what broke and why. It uses Dash0 credits, and organization admins can turn it off for everyone.

Any query in the Log Explorer, Trace Explorer, or Web Events Explorer can now be exported to a file. The button sits in the table header next to the display menu, with CSV as the primary action and TXT, JSON, and YAML in the disclosure menu.

You can now manage Dash0 teams as code using the Dash0 CLI, Terraform provider, and Kubernetes operator, so team definitions live in the same repository, review process, and rollout pipeline as everything else.

The new Spans Table widget brings a sortable, self-refreshing table of spans to your dashboards and the query builder.

The old "Events & Logs" tab in the span sidebar is now "Related logs & events", offering you a one time-ordered list that interleaves log records and span events across the whole trace, resource, or both.

Full AWS Lambda observability is now in Dash0. Connect your account and see every function immediately, instrument to get traces with event payloads, correlated logs and synthetic traces for the failures that never produce telemetry.