• Filter and search in Reliability Roll-up reports

Release details​

new

Filter and search in Reliability Roll-up reports​

Reliability Roll-up reports can span dozens of folders and resources. To make large reports easier to navigate, you can now search, filter, and sort the reliability drill-down tree without modifying the underlying report scope.

Search
In the Find in report field, enter your search phrase. The search highlights matches, expands the first matching folder, and lets you jump between results using Enter or the arrow buttons. Search requires at least three characters and is case-insensitive.

Filters
Click Show filters to narrow the drill-down view by:

• Text to display only resources containing the entered string (min. three characters, case-insensitive)
• Labels to view resources with the labels attached to the resources in the report
• SLO adherence to focus on off-target or on-target SLOs, or on SLOs with no data available

The Statistics block updates automatically to reflect the scores of the filtered resources.

Sorting
Sort the reliability drill-down tree by Name or Reliability score, in ascending or descending order. Sorting applies recursively from the topmost to the deepest layers. For Custom reports, Original order is also available to restore the structure defined at report creation.

Shareable filtered views
All view settings—search terms, filters, and sorting—are persisted in the URL. Copy and share the URL to give teammates a direct link to your current filtered view.

Documentation updates​

• Organization status—a real-time view of your system's health
• Dash0 integration

• Sumo Logic ABC pattern-based queries
• Increased label limit per resource

Release details​

new

Organization status​

We're excited to announce the rollout of the Organization status feature that provides the capabilities of real-time disruption monitoring across your organization, system, or application performance right from the Nobl9 Web application. It gives SREs, engineers, product owners, managers, and support teams a shared, SLO-aware view of operational health without navigating individual SLO configurations or external status pages.

Organization status is built around three core views:

• Status page
• Impact monitor
• Component map

Status page​

The Status page is the main real-time view showing the health of your organization's components. It reflects the current operational state and provides a 90-day historical timeline per component, so teams can assess system health and track changes over time at a glance.

• Overall status reflects the most critical status across all components.
• Component timeline propagates the most critical status from an impacted component upward.
• Disruption registry provides a chronological journal of the 100 most recent disruptions across components.

Any user can search and filter by component name, status, or label, and flag issues directly from this view. Organization admins can register, update, clear, and delete disruptions and handle issues.

Impact monitor​

The Impact monitor tab (admin-only) provides an aggregated view of all issues and impacted components across your organization.

• Summary tiles show the count of impacted components and time-based issue volume breakdowns.
• The Impact scope table lists impacted components.
• The Latest issues table provides a chronological log of all issues.

Component map​

The Component map is an admin-only tool for building and managing the hierarchical structure of your organization's components. It allows nesting components to reflect organizational dependencies and linking SLOs with attached alert policies to streamline automatic disruption detection.

Key capabilities:

• Add components and nest them to mirror your organizational structure.
• Link SLOs to terminal components to feed SLO alert signals directly into Organization status.
• Drag and drop to reorder components within the same hierarchy level.
• Move, edit, or delete components, including all their nested subcomponents, linked SLOs, and associated disruptions.

Disruption detection and management​

Disruptions drive component status changes in Organization status and can be triggered in two ways:

Auto-detection—the system automatically transitions a component to Degraded performance when issues aggregated in 5-minute intervals exceed the following default thresholds:

• 5 issues in 5 minutes for user flags or external telemetry signals
• 2 issues in 5 minutes for Nobl9 SLO alerts

Manual registration—Organization admins can force a component into Degraded performance or Major outage immediately, without waiting for thresholds. Admins can also escalate an auto-detected disruption to Major outage, update context, clear a resolved disruption, or permanently delete it.

Component statuses propagate upstream automatically. If a child component is disrupted, all parent components inherit the most severe status.

Issue sources​

Issues that contribute to disruption thresholds can come from three sources:

• User flags—any user with access to Organization status can flag an issue for a component from the Status page or the component details page.
• Nobl9 SLO alerts—SLOs linked to components automatically send triggered alerts as issues.
• External telemetry—third-party tools can send issue signals using the new POST /status-page/issues/external API endpoint.

Component and disruption details​

Clicking a component name opens the component details page, which provides a deep dive into that component's health history, linked SLOs, and associated issues, along with admin controls for registering and clearing disruptions.

Each disruption has its own disruption details page, accessible from the Disruption registry. It displays full context including severity, trigger type, duration, event timeline, and all contributing issues.

Access control​

Organization status follows Nobl9's role-based access model:

new

Dash0 integration​

Nobl9 now integrates with Dash0, an OpenTelemetry-native observability platform with a Prometheus-compatible API. You can connect Dash0 as a data source and use standard PromQL to build SLOs on top of your high-resolution telemetry.

Both connection methods are supported:

• Direct connection—authenticate using a Dash0 Auth Token and the server URL, configured directly in Nobl9 without deploying an agent.
• Agent connection—deploy the Nobl9 agent with the DASH0_AUTH_TOKEN environment variable to authenticate requests.

Both threshold and ratio SLO metric types are supported using standard PromQL syntax.

improved

ABC pattern-based Sumo Logic queries​

Sumo Logic Metrics SLOs now support multi-query (ABC pattern) mode, consistent with Sumo Logic's native query chaining syntax.

With ABC pattern queries, you define up to six individual metric queries in lettered rows (#A–#F) and combine them into a single mathematical formula in the final query row. The resulting formula defines the SLI for the objective.

For example, to track an error rate:

Query #A:  metric=request_count
Query #B:  metric=request_count status_code=5*
Query #C:  (#B / #A) along service, env

• Capabilities
  • ABC pattern queries are available for Metrics SLOs only. Logs SLOs continue using the single-query format.
  • You can add or remove individual rows as needed.
• Configuration
  • Existing single-query SLOs are automatically normalized; they remain fully backward compatible.
  • In YAML, use either sumoLogic.query (single) or sumoLogic.queries (ABC pattern), but not both.
• Requirements
  ABC pattern-based syntax is supported as Beta. This means your Sumo Logic data source must meet these requirements:
  • Agent connection—version 0.109.0-beta / 0.110.0 or higher

improved

Increased label limit per resource​

You can now add up to 100 labels per resource—SLOs, services, projects, alert policies, and annotations. This applies across the Nobl9 Web, API, and YAML resource definitions.

Documentation updates​

• Token-based authentication for ServiceNow alert method

Release details​

improved

Token-based authentication for ServiceNow alert method​

Secure your ServiceNow alert method integration with new token-based authentication. This provides a stable and resilient alternative to basic authentication for all Nobl9-to-ServiceNow connections.

To use this method, provide the REST API token generated for your ServiceNow instance instead of standard user credentials:

The YAML configuration now supports the apiToken field. Use it instead of the username and password required for the basic authentication:

  servicenow:
    apiToken: servicenow-rest-api-token
    instanceName: servicenow-instance-name

Documentation updates​

• Export SLO list as CSV

• Preview SLOs in Reliability Roll-up reports

Release details​

new

Export SLO list as CSV​

You can now export the SLO list as a CSV file for easier reporting, sharing, and offline analysis. The exported CSV reflects your current SLO list configuration, including:

• Applied filters
• Displayed columns

To export the list, go to Service Level Objectives, switch to the SLO list, and click next to the column customization menu.

improved

Preview SLOs in Reliability Roll-up reports​

Investigating reliability issues in the Reliability Roll-up report is now faster. In the Reliability drill-down tree, you can hover over an SLO name to preview its reliability burn down chart without leaving the report.

From the preview, you can also copy the link to the SLO or open its details page for deeper analysis.

• Filter by layer in Highest and Lowest reliability score tables of Reliability Roll-up reports

Release details​

improved

Filter the reliability score ranking tables by layer​

Auditing peak and baseline performers shouldn't mean scrolling through every folder. With this update to Reliability Roll-up reports, you can now filter out the clutter and focus on specific report layers. Click on a table to narrow your view:

• Nobl9 MCP server

• Usability improvements in Reliability Roll-up reports

Release details​

new

Nobl9 MCP server​

The new Nobl9 MCP server enables direct connection between AI clients and the Nobl9 platform. This allows you to use AI agents to request SLO health and other resources data without a manual login to the Nobl9 platform.

Key highlights:

• Wide AI client support
  Setup guides are available for ChatGPT, Copilot in VS Code, Gemini CLI, Claude Code, Codex, and OpenCode.
• Safe access to your Nobl9 resources
  Ask for SLO health metrics, search SLOs by keyword, label, or type, retrieve resource definitions, and inspect user and access control details.
• OAuth 2.0 authentication
  Secure browser-based authentication with support for refresh tokens and authorization server metadata discovery compliant with RFC 8414 and RFC 9728.
  If your AI client doesn't support pre-provisioned client IDs, use the sloctl mcp proxy to connect locally.

improved

Reliability Roll-up report usability improvements​

To help you make decisions faster, the Least reliable and Most reliable ranking tables in Reliability Roll-up reports are now called Lowest reliability score and Highest reliability score. With these clearer titles, you can instantly spot underperformers and top achievers in your system at a glance.

Documentation updates​

• Nobl9 Alerts mobile application
• Data consolidation options in composite SLOs

• Replay performance improvement

Release details​

new

Nobl9 Alerts mobile​

We are excited to introduce the Nobl9 Alerts mobile application, designed to help you respond to SLO alerts anytime, anywhere. It offers a native experience for SREs, DevOps engineers, and on-call personnel to manage the entire alert lifecycle—from triggering to resolution—directly from their mobile devices. With the Nobl9 Alerts app, you'll have critical service health information at your fingertips, enabling you to respond to incidents on the go.

The app allows you to:

• Stay on top of alerts—See all triggered and resolved alerts in one place. You can quickly filter by status, severity, and other criteria to find what needs your immediate attention.
• Get the full context—View associated SLOs, detailed descriptions, labels, and contextual charts to understand the impact and history of every alert.
• Reduce alert fatigue—Silence noisy alert policies during a major incident or planned maintenance. You can also view and resume previously silenced alerts.
• Collaborate with your team—Copy a link to an alert and share it with your team to resolve incidents faster.

The Nobl9 Alerts app is available for both iOS and Android.

improved

Data consolidation options for composite SLOs​

Composite SLOs aggregate data from multiple components to form a single, unified value. Previously, component reliability was the only metric available for calculating the composite's reliability, using a weighted mean of each component's per-minute reliability.

This release introduces another aggregation metric: error budget state. Error budget state method considers whether each component has any error budget remaining. The composite's per-minute reliability is then calculated based on the weighted mean of components that have a positive error budget.

The aggregation metric selection is available in the composite SLO wizard in Step 2: Components, within the Data consolidation block. For users of the SLOs-as-code approach, the YAML configuration must contain the aggregation field with either the Reliability or ErrorBudgetState value:

apiVersion: n9/v1alpha
kind: SLO
metadata:
name: user-journey
displayName: User journey
project: customer-facing-applications
spec:
budgetingMethod: Occurrences
objectives:
  - displayName: Excellent
    name: excellent
    target: 0.96
    composite:
      maxDelay: 15m
      components:
        objectives:
          - project: servers-and-databases
            slo: CPU usage
            objective: excellent
            weight: 3
            whenDelayed: CountAsBad
      aggregation: ErrorBudgetState
# The rest of your composite SLO configuration

The default aggregation metric is Reliability.

improved

Replay performance improvements​

This release improves Replay performance and the time it takes to retrieve and calculate historical data. The improvement is especially noticeable when replaying SLOs for longer time periods.

Documentation updates​

• Moving SLOs between services in the same project

• Search functionality in Reports
• Streamlined SLO details page

• Optimized performance of Service health dashboard

Release details​

new

Moving SLOs between services in the same project​

Organizing your SLOs just got more flexible. You can now move SLOs between different services within the same project, just as you already could between projects.

This gives you more flexibility to restructure your SLOs as your services evolve. Because the SLO's unique link remains unchanged, this move won't break any alerting or resource definitions that rely on it. Access permissions also remain intact.

Keep in mind that this action can affect reports that are filtered by the SLO's original or new service. The SLO will also inherit the review settings of its new service.

improved

Search functionality in Reports​

Navigating a long list of reports is now much faster. We've added a search bar to the Reports section to help you find what you need in an instant.

Start typing a keyword from a report's name, and the list will filter as you type. It’s a small change that makes a big difference in your workflow.

improved

Streamlined SLO details page​

We've tidied up the SLO details page to make handling charts and objectives more straightforward. Here’s what’s new:

• Chart management relocated
  The Charts option is renamed to Manage charts and is now tucked into the More actions menu for a cleaner look.
• Objective selection
  When an SLO has multiple objectives, the Select objectives option now appears when you're on the Objectives tab, making it easier than ever to focus your view.

improved

Optimized performance of Service health dashboard​

We have reverted the "list-on-hover" feature on the Service health dashboard to a "click-to-view" model. This change addresses performance issues that were observed with large dashboards.

• Service health dashboard enhancements
• Improved Annotations switcher visibility

Release details​

improved

Service Health dashboard enhancements​

Two key usability improvements in the Service health dashboard streamline your monitoring workflow and reduce friction when analyzing service health:

• Instant SLO list on hover
  View the list of SLOs within a service by hovering over your required service circle.
• Persistent cross-view filters
  Your applied filters stay put, so the context remains intact each time you switch perspectives between the error budget and burn rate dashboard views.

improved

Improved Annotation switcher visibility​

The Annotations switcher on SLO details is repositioned and enhanced for better annotation handling.

The switcher now sits directly above the objective name row, providing a clear visual cue for users. Next to it, you'll find a menu for granular control over which annotation types appear on the charts.

• Refined SLO metadata block
• Replay's default period matches the SLO time window

Release details​

improved

Refined SLO metadata block​

The SLO metadata block, the gray collapsible area on the SLO details page, is now packed with even more information. It's organized into sections, making it easier to find key information about the SLO, including:

• SLO name and description
• SLO creation and update details
• Responsible users for the SLO's service
• SLO configuration—time window, budgeting method, data source and its parameters
• Review summary
• References and context with any additional labels or links

improved

Replay's default period matches SLO time window​

Now, when you trigger a Replay, the pre-selected period defaults to the SLO's entire time window. You can still adjust the period manually or proceed with the suggested default.

Documentation updates​

• Refined System Health Review reports
• Enhanced label details and handling

Release details​

improved

Refined System Health Review reports​

This version brings simple yet impactful enhancements to System Health Review reports! Now your system health assessments can be more streamlined and tailored than ever before. While all grouping options are refined, the custom rows grouping unlocks ultimate customization.

• Collapse the grouping type selector to maximize screen space for your layout.
• With the custom rows grouping, personalize the row header by giving the top-left cell a name that clarifies the context at a glance.

• Edit column and custom row names your way: double-click for a quick inline change, or single-click to open the full modal.
• Drag and drop to reorganize columns (and rows, for the custom rows grouping) on the layout you build.

Additionally, when you're switching between grouping options, your layout configuration is saved throughout your editing session.

improved

Enhanced label details and handling​

The label details screen is now a full-page view accessible with a dedicated link. The improved page features a collapsible summary. Click to see a breakdown of all labeled resources.

Documentation updates​

• Custom row grouping in System Health Review reports
• Drag & drop columns to organize the Events table and SLO/service lists

Release details​

improved

Custom row grouping in System Health Review reports​

This version adds more flexibility to System Health Review reports by letting you group rows by labels.

Now, you can fully customize the layout of your report table, including row headers and the SLOs they display, instead of being limited to grouping by projects, services, or label values.

To use this feature, select the Custom rows grouping option when defining your report layout. Then, for each row, you can set a name and choose the labels that define which SLOs it will include—just like you do for columns. You can also add and remove rows with this layout grouping.

improved

Drag & drop columns in resource lists​

We've also improved the customization menu in the Events table and the SLO and service lists.

Now, instead of using move up or move down controls, you can drag and drop columns into your preferred order.

Documentation updates​

• Active data anomalies tile on SLO details
• Automatic annotations on SLO edits

• Saved the last-visited view for the Service Level Objectives section
• Hide the Ungrouped SLOs category in the System Health Review report

Release details​

new

Active data anomalies tile on SLO details​

For immediate visibility into data quality issues, the SLO details page now features a new Active data anomalies tile.

This tile is located next to the Active alerts tile and displays a real-time count of all unresolved data anomalies affecting your SLO. It helps you instantly spot potential problems with your data source or query configuration that could impact the accuracy of your SLO calculations.

The count includes both manually configured and automatically detected anomalies and updates in real-time as they are detected or resolved. This enhancement ensures you have a complete, at-a-glance overview of your SLO's data integrity.

new

Automatic annotations on SLO edits​

To improve traceability and provide a clear audit trail, Nobl9 now automatically generates an annotation every time an SLO is edited. These annotations help you track an SLO's history and diagnose how changes impact its performance. Whenever an SLO is edited, an annotation is added to its chart, detailing:

• What changed—A YAML diff view clearly shows the differences between the previous and current configurations.
• Who and when—The user who made the change and the exact time of the edit.
• Change origin—The source of the modification (Nobl9 UI, sloctl, Terraform provider, or an SDK).
• Budget impact—An indication of whether the change impacted the SLO's error budget.

You can filter for these annotations in the Events section using the User > SLO edits filter. Additionally, the user who made the change can edit the annotation to add more context.

This feature is now active for all SLOs.

improved

Saved last-visited view for the Service Level Objectives section​

To create a smoother and more personalized experience, the Service Level Objectives page now automatically remembers your last-used layout.

The page offers two distinct views: a high-level SLO grid and a detailed SLO list. Previously, the page would always default to the grid view. With this update, your selection is saved, so if you prefer the list view, Nobl9 will open directly to it on your next visit.

This is especially helpful for users who frequently use the detailed list view. With its rich filtering, column sorting, and display options, this view acts as a powerful SLO explorer, allowing you to investigate your SLOs from various perspectives.

You can switch between the grid and list views using the buttons in the upper-right corner of the Service Level Objectives page:

improved

Hide Ungrouped SLOs in System Health Review reports​

For a cleaner, more focused view in your System Health Review reports, you can now hide the Ungrouped SLOs row. This new option is available when using the Label value rows grouping.

The Ungrouped SLOs row gathers all SLOs that meet your report's filter criteria but do not have the specific label used for grouping. By hiding this row, you can focus your analysis on the categorized SLOs that are most relevant to you.

Documentation updates​

• SLO oversight rollout
• API keys

Release details​

new

SLO oversight​

We're excited to announce the full rollout of SLO oversight—an approach and toolset that helps teams keep SLOs relevant, trustworthy, and integral to their daily workflows. It adds a program-level dashboard, service-level review cycles, automatic data anomaly detection, advanced resource lists, and an expanded events catalog.

SLO oversight dashboard​

The SLO oversight dashboard provides a unified view of your SLO program's health and quality. Its key features include:

• A summary of service and SLO health
• Highlights for at-risk services and those with exhausted error budgets
• Identification of SLOs with review debt and data anomalies
• Links to filtered service and SLO lists for swift triage, and to Events with a focus on data anomaly annotations

SLO reviews with service-level cycles​

This feature introduces repeatable review schedules with service ownership, tracked at the service level and inherited by the service's SLOs.

• Assign responsible users at the service level and schedule a review; these settings are then applied to all SLOs within that service.
• The SLO review status and schedule appear in the service and SLO lists and details.
• The entire review history is recorded using editable annotations generated automatically upon status transition.

Data anomaly detection​

Automatic data anomaly detection is part of the SLO quality monitoring integrated with SLO oversight.

• Data anomalies are surfaced on the dashboard and funneled into Events for closer examination.
• This is useful during reviews, as data anomalies can indicate whether an SLO needs to be updated or simply verified.
• Manual configuration for "no data" anomalies is still available.

Advanced service and SLO lists​

You can now use customizable tables with preset views and advanced filtering based on SLO oversight categories.

• Table presets for quick access
• Expanded filtering by data anomaly, error budget remaining, review status or date, responsible user, and more
• Additional table columns to tailor the list to your needs

Find answers to questions like:

• Which services have the most SLOs with overdue reviews?
• What should my next focus be?
• Which services my team is responsible for are healthy?

Expanded Events​

Events now provide a unified activity trail that includes SLO oversight categories:

• New SLO review and data anomaly events
• Filter by data anomaly type, error budget status, labels, actors, and other criteria

Ready to jump in?​

• Access the SLO oversight dashboard in the Dashboards section in the Nobl9 web application.
• Your Organization admin can filter resources to create a standardized organizational view.
• Data anomaly detection uses default detection rules. Contact Nobl9 Support if you need to change them.
• The SLO oversight dashboard and all its features use Nobl9's standard organization- and project-level access permissions.

new

API keys​

More great news! This release also introduces enhanced programmatic access through API keys.

API keys are our new mechanism for authenticating programmatic requests to the Nobl9 API and sloctl. They are intended to streamline control and security when integrating with your CI/CD pipelines and infrastructure-as-code workflows.

Key highlights:

• Clear identity management
  Using API keys ensures clear identity management for automation users.
• Dedicated management console
  Organization admins can manage API keys from the dedicated Settings > API keys section in the Nobl9 web application.
• Flexible key control
  Create, activate, deactivate, or delete API keys as needed for enhanced security hygiene.
• One-time secret display
  For security, the Client secret is only displayed upon creation.
• Optional expiration policy
  Organizations can request to enable an automatic expiration policy to enforce regular key rotation, ensuring compliance and minimizing risk.

Documentation updates​

• Group rows by label values in System Health Review reports

Release details​

new

Row grouping by label value in System Health Review reports​

This enhancement introduces greater flexibility to reporting. You can now group rows in your System Health Review reports by label values. To configure this grouping, select a label key, and its values will automatically populate the report rows.

Additionally, a row with ungrouped SLOs appears if the report contains any SLOs that meet the column criteria but lack the label used for row grouping. This ensures that all relevant data is included in the report.

Nobl9 applies the standard filter combination logic to display SLOs in the report.

Documentation updates​

• New data anomaly types

Release details​

new

New data anomaly types​

We're excited to announce a significant enhancement to our automatic data anomaly detection capabilities for Nobl9 Enterprise Edition users. Nobl9 now automatically detects three new types of data anomalies to provide deeper insights into the data integrity of your SLOs:

• Constant burn triggers when an error budget burns continuously
• No burn identifies SLOs that aren't burning any budget for an unusually long time
• Incremental mismatch detects when a ratio SLO with an incremental data count method receives a non-incremental data point

These new detection types act as intelligent assistants, highlighting potentially problematic SLOs that might otherwise go unnoticed. Automatic data anomaly detection, including the No data type, is enabled for all SLOs. It utilizes the centralized waiting time and cooldown defaults, which can be fine-tuned upon request to Nobl9 Support, and operates seamlessly alongside manually configured No data detection.

Auto-detected data anomalies are recorded as SLO annotations. Nobl9 adds the ~anomaly-rule: auto label to such annotations to distinguish them from the annotations for manual No data anomalies.

This feature empowers you to proactively refine your SLOs and ensure they accurately reflect your system's reliability.

Documentation updates​

• The Labels column in the SLO list
• Extended SLO information on service details

Release details​

improved

The Labels column in the SLO list​

You can now add a Labels column to the SLO list to view the labels assigned to your SLOs.

By default, the Labels column is hidden. To display it, select it from the column customization menu.

improved

Extended SLO information on service details​

The SLOS tab on the service details page has been enhanced to display the following information:

• SLO name
• SLO objectives
• Reliability score
• Remaining error budget
• Last modification date and time

• Step parameter in Prometheus-based data sources

Release details​

improved

Step parameter in Prometheus-based data sources​

Prometheus-based data sources now require the Step parameter to set the metric resolution retrieved by Nobl9.

With it, you can tailor your SLO queries to incoming metric granularity.

The Step parameter accepts any whole positive number measured in seconds. For best results and data accuracy, we recommend the following:

• Using a Step of at least 15 seconds
• Ensuring that the Step is not greater than the query interval set for your data source

Documentation updates​

• Name and Display name character limit is 253
• User annotations renamed to Comment
• No data annotation template enhanced

Release details​

improved

Name and Display name character limit is 253​

The character limit in the Name and Display name fields has been significantly increased—from 63 to 253 symbols. This enhancement provides you with greater flexibility to craft more descriptive and meaningful names, while the other requirements for the Name (name) field remain unchanged.

improved

User annotations renamed to Comment​

The User annotation category is now Comment. This clearly distinguishes annotations manually added by users from those generated by the system.

improved

No data annotations template enhanced​

The enhanced No data annotations provide more context to help you troubleshoot missing SLI data. In addition to the existing information, the following details are displayed:

• The annotation rule label.
  It indicates how the data anomaly was detected
  • ~annotation-rule: manual—the No data anomaly was detected by a user-defined rule configured for this specific SLO
  • ~annotation-rule: auto—the no data anomaly was detected by a system-defined rule. This default rule is the same for all SLOs and cannot be changed by a user
• The duration of the no data period
• Troubleshooting hints
• Reference information
  • The name of the objective that is missing data
  • When the objective last reported a data point
  • When the data anomaly was detected (including the waiting time set in the detection rule)

Documentation updates​

• Health overview preset and SLO type filter in the SLO list
• Health overview columns in the service list

Release details​

improved

Health overview preset and SLO type filter​

We've enhanced the SLO list to help you analyze SLO performance more efficiently. These new additions make it easier to get a quick overview and find exactly what you're looking for.

Health overview preset

Get an instant snapshot of your SLOs' health. This new preset automatically displays health-related columns: Reliability and Error budget. It’s the fastest way to assess performance without customizing columns manually.

Red reliability and error budget values indicate the SLO needs your attention.

💡Column customization

As always, you can create and save your own custom view by selecting Edit and apply my view from the column customization menu

SLO type filter

Distinguish between foundational and multi-level SLOs. This filter helps you narrow the list to focus on either:

• Standard SLOs—core, single-level SLOs based on one data source

• Composite SLOs—multi-level hierarchy SLOs that combine standard and other composite SLOs as components, receiving data from multiple data sources

improved

Service health overview columns​

You can now assess the health of your services directly from the Catalog's service list, saving you time and clicks. We've integrated category thresholds from the Service health dashboard by error budget, allowing you to see which services need attention without navigating away from the list.

The new columns include:

• Service health categories
• SLOs per category—the number of SLOs within each service that fall into health categories

To show and hide columns, click Customize columns as you did before.