Skip to main content

Nobl9 application (1.193.0)

ยท 3 min read
We've just released Nobl9 1.193.0! Release highlights:
keep up to date!
Keep tracking the latest changes in Nobl9 and subscribe to our Application RNs RSS Feed
new
improved
fixed

Release detailsโ€‹


new
Count delta metrics in the Prometheus APIโ€‹

The Prometheus API for SLO time series now exposes count_good_delta and count_total_delta, which report the increment since the previous sample. Both are also available pre-aggregated at 1-minute, 5-minute, 15-minute, 1-hour, and 1-day resolutions.

Unlike count_good and count_total, which cover the whole SLO time window and can decrease as older observations leave it, the delta metrics report fresh increments only. This makes them a better fit for analyzing event volume over time. See the count delta metrics reference for details.

improved
Expandable annotation windowโ€‹

You can now expand an annotation popover into a larger, viewport-centered window with the new expand control next to Close. The header and Description section stay visible while the annotation content scrolls independently, making long descriptions easier to read and edit.

improved
Multiple active disruptions per componentโ€‹

The disruption API now allows multiple active disruptions to share the same origin component. Previously, a component could have only one impacting disruption at a time.

The component's status continues to reflect the most severe active disruption. The activeDisruptionId field in API responses now refers to the newest active disruption.

improved
Release update indicator in Help & Resourcesโ€‹

The Help & Resources menu now shows a notification dot when new Nobl9 release notes are available, so you can spot product updates without leaving the app.

fixed
Anchored regex label matchers in the Prometheus APIโ€‹

Regex label matchers in Prometheus API queries are now anchored, matching the behavior of native Prometheus.

Previously, a selector such as slo=~"name-a|name-b" could also match SLOs whose names merely contained one of the alternatives. This over-matching could inflate a query's series count and fail the query with a query selects N series, which exceeds the maximum error.