6 updates shipped to Dash0 in February 2025: Enhanced Email Notifications and Channel Controls, Slack Bot Integration for Notifications, Automatic OpenTelemetry schema migrations and more.
Introducing a series of email-centric alerting enhancements designed to provide more insights at a glance.
We have introduced a series of enhancements to our email notifications to allow you to get more insights into failed checks at a glance and improve control over the notifications you receive.
Our email notifications have been redesigned to include the same familiar affected resource breakdowns previously available only within the product. This update ensures you receive these insights directly in your inbox even before you open the failed check in Dash0.
In response to user feedback, we've introduced the ability to configure multiple email recipients within a single notification channel. This features simplifies collaboration by ensuring that all relevant stakeholders receive timely updates, keeping your team synchronized and informed.
Building upon recent updates, you now have greater control over the frequency of periodic reminders for unresolved failed checks. This per-notification channel setting allows you to tailor alert intervals to your operational needs, reducing notifications fatigue and enhancing focus on critical issues.
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 has introduced a new Slack Bot integration to enhance real-time alerting within your team's Slack workspace. This feature allows you to receive immediate notifications directly in your chosen Slack channels, ensuring that failed checks are promptly addressed.
Instant Notifications: Receive up-to-date notification for failed checks directly in your specified Slack channels, facilitating swift responses to potential problems.
Threaded Discussions: Each alert initiates a Slack thread, maintaining organized discussions and tracking the history and evolution of incidents in a centralized location.
Quick Access Links: Hyperlinks embedded within check rule annotations are parsed and prominently displayed at the top of each alert, providing immediate access to relevant resources and dashboards for efficient troubleshooting.
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.
OpenTelemetry semantic conventions regularly gets updated, where attributes or even metric names get changed. For example, http.status_code got updated to http.response.status_code for better consistency with other attributes.
For engineers to keep all names up-to-date, this can be very cumbersome work and where it is easy to miss some instrumentation sources, resulting in inconsistent attributes. This makes querying difficult, as not all signals will get in- or excluded as expected. Also Views or Dashboards might not work as expected.
Dash0 now supports executing the migrations as defined by the OpenTelemetry schemas itself. Via settings, the user can pick whether to always update to latest, or to one specific version from the list:
A specific version can be pinned to prevent e.g. breaking dashboards in the future, when new migrations become available. Signals will never get downgraded to a specified version.
We removed Dash0's base subscription fee, moving to a purely consumption-based model with the same rates we have had from the beginning.
Keeping things simple for our end users is one of the core values of Dash0. After reviewing our pricing, we realized we could make it even simpler.
From the start, our price is based on counting metric data points, spans and span events, and log records. This allows you to send us your telemetry irrespective of how much metadata you have on it, and we actively encourage you to send all the metadata you think necessary or useful, irrespective of how many GB it is. We also do not have per-seat pricing: we want everybody in your team to be able to enjoy and benefit from Dash0.
Up until today, we had a $50 subscription fee, which included 100 million metric data points, 25 million spans and span events, and 25 million log records. The $50 wasn’t chosen at random: it is the amount you’d pay for sending that much data in a month.
Today, we are removing our base subscription fee. Effective midnight of Friday, February 7th 2025, Dash0’s pricing works purely consumption-based using the same rates as before:
$0.20 for 1 million metric data points
$0.60 for 1 million spans and span events
$0.60 for 1 million log records
For most Dash0 users, the amount due in the bill will be the same. But the bill itself will be easier to read, and the pricing simpler to understand.
And for users who have been sending less telemetry than what was included in the base subscription, Dash0 just got even cheaper!
I am sending less telemetry than what is included in the base subscription fee and my billing cycle ends after February 7th. Will I pay one more month of the base subscription fee?
No, we are waiving the base subscription fee of all current billing cycles. That is, every billing cycle beginning on or after January 7th will be charged with the simpler consumption-based model for the entirety of the data you sent us in that billing cycle. For example, if you sent us 1 million logs, 2 million spans and 4 million metric data points during the current billing cycle that started after January 7th, you will pay 1x $0.60 + 2x $0.60 + 4x $0.20 = $2.60.
I send a lot of spans and logs, but only a few tens of millions of metric data points. Will my bill be cheaper with the new model?
Yes, you will only pay the millions of metric data points you send, not at least 100 millions like before. You can save up to $20 per month (100 million, charged $0.20 per million). Similar math can be done for spans and log records.
So I could have Dash0 bills that go down to zero?
If you do not send us any telemetry in a billing cycle, we charge you nothing. You’ll still receive a $0 invoice for bookkeeping purposes.
Will you delete my organization and my telemetry and configurations in it if I don’t send telemetry for an entire month?
No. You paid for that telemetry and you get the full retention period on it. For metrics, it’s 13 months, so you have the right to your organization for at least that after you stop sending telemetry.
If I delete my Dash0 organization in the middle of a billing cycle, do I still get an invoice at the end of it?
Yes, you get one last invoice for the amount of telemetry sent since the beginning of the last billing cycle.
A lot of the logs that are sent to Dash0 are unstructured: they are strings of text, with important information like severity, “hidden” inside the message. Until recently, such logs have been marked in Dash0 logs as having severity UNKNOWN. But this is a thing of the past.
Our log ingestion pipeline uses AI to understand the log structure of applications and automatically extract the severity. Previously in Beta, this capability is now available for everyone, out of the box. And at no extra charge!
Logs with known severity like INFO, WARN and ERROR are not only easier to filter in the UI, but can also be used as system health indicators when setting up dashboards and check rules.
Log AI in action: Shortly after the capability was enabled, logs with unknown severity (in grey) were replaced with color coded logs, also highlighting a couple errors and warnings that would have been indistinguishable otherwise.
