Dash0 Raises $110M Series B at $1B Valuation

Last updated: July 7, 2026

Alert on SLOs

How to alert on SLO burn rate in Dash0 using check rules, and what the built-in burn-rate alerting will add post-GA.

SLO alerting is based on burn rate — how fast you are consuming your error budget — rather than on individual threshold violations.

Alerting during the Private Beta

Today, alerting on SLOs is done through Dash0 check rules. SLOs are evaluated continuously and expose a set of SLO metrics — including ready-made fast burn and slow burn rate metrics — and you create burn-rate check rules against those metrics.

A common pattern uses two signals:

  • Fast burn — a high, short-lived burn rate (about 14.4×, roughly 5% of a 30-day budget in about an hour) that warrants an immediate page.
  • Slow burn — a lower burn rate (just above 1×) sustained over a longer window, which still threatens the budget but is less urgent.
Metric names are changing

The exact SLO metric names exposed by the recorder are being finalized. Confirm the current metric names with the SLOs team before publishing concrete check-rule examples.

OpenSLO alertPolicies

If you import an OpenSLO definition that includes alertPolicies, Dash0 accepts the definition but ignores those policies — the SLO still computes correctly. Configure alerting with check rules as described above.

Coming after GA

A built-in, multi-window multi-burn-rate alerting experience (based on Google SRE guidance) is planned for after the Private Beta, building on the fast and slow burn metrics that are already available today. It is expected to include:

  • Fast burn — a short window that detects rapid budget consumption for an immediate page.
  • Slow burn — a longer window that catches sustained, lower-rate consumption.
  • SLO violation — a dedicated alert when the objective itself is breached.

You will be able to route each alert type to the notification channels you choose. Thresholds and channel routing are still being defined.

Further reading