Dash0 Release Notes

We're excited to announce our new Hierarchy Map widget, which provides an intuitive way to visualize a large number of resources and their relationships in a condensed and clear manner. This powerful visualization helps you quickly understand the structure and health of your infrastructure as you wish.

The dash0-enabled annotation allows you disable or enable of check rules in Infrastructure-as-Code.

We're excited to announce the release of our two new alerting integrations "ilert" and "Discord". These integrations provide real-time notifications, similar to already existing integrations like Slack Webhook or Google Chat, ensuring you stay informed about critical issues as they arise.

Dash0 now supports a Terraform provider to manage your configuration as code.

We are thrilled to introduce two new integrations that enable you to receive real-time alerts directly in Microsoft Teams and Google Chat. This enhancement ensures you are immediately notified of critical issues and can act swiftly to resolve them.

Our LogAI now identifies patterns in your log messages and uses them to extract type-safe, named attributes that you can use in queries, filters and grouping and, last but not least: triage.

We’ve introduced a new Home Page that gives you a high-level overview of all telemetry sent to Dash0, including metrics, logs, traces, and alerts—so you can spot issues faster and stay on top of your system’s health at a glance.

We're excited to announce our new integration with PagerDuty, which enables you to use PagerDuty as a notification channel.

We are pretty fond of the growing OpenTelemetry support in Linkerd.

We've just added a new feature to our recently released Slack Bot integration: chart images. This update provides an enhanced way to visualize and understand your alerts directly within Slack.

We love interacting charts. We think you should be able to get answers by interacting with data visualizations in intuitive ways. This is why since early on, Dash0 allowed you to focus on a smaller timeframe by creating a selection on a chart and using the Set Time Range button.

With the latest release of the Dash0 operator, you now have not only one, but two powerful mechanisms to only collect the telemetry you really need in your Kubernetes clusters: Filters and transformations. Both capabilities help to reduce the noise in your telemetry, let you focus on what really matters to keep your services running smoothly, and ultimately also help to save hard cash.

We taught Dash0 to leverage the wealth of telemetry metadata you send to find commonalities, differences and patterns. We call it Triage, and it is a pretty simple experience: you draw a box around what interests you, and let Dash0 tell you why it is so very interesting.

OpenTelemetry, Prometheus and other open-source projects have made telemetry open, easy to collect and plentiful. Too plentiful, sometimes: not all telemetry is equally valuable to everyone.

The Dash0 operator can now filter with namespace-specific rules the telemetry it collects before sending it to Dash0. This feature is the "client-side" equivalent of Dash0's Spam filters, which also becomes available today.

Tired of sifting through endless streams of logs and traces? Within the Logging and Tracing Explorers, you can now group by attributes to quickly get an overview! Grouping unlocks yet another way to iteratively reduce the amount of data you are sifting through to get from data to answers.

The Tracing Heat Map is very powerful and provides an intuitive way of detecting outliers in terms of slowness or clusters of errors in the blink of an eye. (And now with no more Lost in Time issues, getting a first peek at the offending spans is so easy!)

Introducing a series of email-centric alerting enhancements designed to provide more insights at a glance.

Dash0's new Slack Bot integration delivers real-time notification, threaded status changes, and quick-access links directly to your Slack channels reducing alert fatigue efficiency.

Dash0 can now automatically update attributes (for Resources, as well as Spans, Logs and Metrics) to their latest naming as defined according to the OpenTelemetry semantic conventions.