Skip to main content

Nobl9 application (1.72.0)

· 2 min read
We've just released Nobl9 1.72.0! Release highlights:
improved
fixed
  • Medium- and high-level vulnerabilities
keep up to date!
Keep tracking the latest changes in Nobl9 and subscribe to our Application RNs RSS Feed

Release details​

improved
Service Health Dashboards: sort by name​

You can now sort resources alphabetically on both Service Health dashboards—by Error Budget and by Burn Rate. The sorting logic is simple: it sorts all resources—projects, services within projects, and SLOs within services—by name in ascending or descending order, regardless of their status.

Sorting remains consistent even if a resource's health changes: the service shifts the category and color, but its location stays the same.

Service Health Dashboard sorting by name
Image 1

improved
SLO details: author and last updated​

Using sloctl and the Nobl9 SDK for Go, you can now identify who created an SLO and when it was last modified.

Run sloctl get slos and check the spec.createdBy and status.updatedAt fields for the required details.

Currently, these fields aren't available through the SLO Status API.

apiVersion: n9/v1alpha
kind: SLO
metadata:
  displayName: My SLO
  name: my-slo
  project: my-project
spec:
  ...
  createdBy: %USER-ID%
  ...
status:
  updatedAt: "2024-03-14T11:06:00Z"

Documentation updates​


Service Health Dashboard:
  • Sort by name logic
  • Services under the No data category: why this occurs
    • Splunk data source: minimal permissions required by Nobl9 agent
    Ratio metrics: requirements and recommendations to query results
    YAML guide
    On this page