eBPF Continuous Profiling released

Latency SLOs on any histogram

Add a duration to an SLO and count only the requests that succeeded within it. It works on span metrics and any cumulative histogram, and you do not write any PromQL.

The Good events card of the SLO form for the demo-webshop-search service on dash0.spans.red. Duration is set to at most 300 ms, the success criteria is otel.span.status.code != ERROR, and the PromQL preview shows the histogram_fraction query the form writes.

A request that succeeds after eight seconds is still a bad experience, but an error-rate SLO counts it as good. To build a latency SLO in Dash0 until now, you wrote the PromQL yourself, with a bucket filter that had to match a bucket bound exactly or a histogram_fraction query.

The SLO form now has a Duration row in the Good events and Bad events cards. Pick a histogram metric, such as dash0.spans.red or http.server.request.duration, and type a duration like 300 ms. A request then counts as good only when it matches your success criteria and finishes within that time. The form writes the query and shows it as you type. It works with span metrics, OpenTelemetry histograms with fixed buckets, and native or exponential histograms.

See the documentation to set one up.