Skip to main content

Replaying SLOs

You can replay SLOs in two non-contradicting ways:

SLOs replayed on creation can temporarily display the No data status in charts and tiles—retrieving and processing historical data consume time. Once data is retrieved and processed, your SLO displays reliability values for this period.

Similarly, when you replay existing SLOs, they display No data over the entire period of historical data retrieval. Data from the preceding period will be displayed without changes.

You can track all Replays and cancel the queued ones in the Job Status widget.

You can also manage the Replay queue using sloctl.

⚠️permanent action

When you replay an existing SLO with calculated error budget, Replay overwrites previous data with the newly fetched. It results in error budget recalculation based on the newly retrieved data, so the reliability values of your SLO can be different once Replay is complete.

This is the reason for Replay's impact on Nobl9 resources connected to your SLO. The dependent resources are:

Learn how Replay impacts resources connected to your SLO.

Replaying SLOs on creation​

If Replay fails
Auto-replay and SLO creation are separate operations. If Replay triggered on SLO creation fails, your SLO will still be created.
However, the error budget calculations for such an SLO start from the first successful timestamp received after creation or editing, without retrieving historical data.

When your data source is configured to replay SLOs on creation, Replay will be launched or queued immediately after you save your new SLO.

  1. Go to the Service Level Objectives section on the Nobl9 Web.
  2. Click .
  3. Select the required data source with the Replay support.
  4. Set Default period for historical data retrieval to a non-zero value.
  5. Click CREATE SLO.

Considering Replay slots availability, Replay for your newly applied SLO will be triggered immediately or queued.

Replaying existing SLOs​

You can manually replay SLOs on the Nobl9 Web or using sloctl.

To replay and SLO, do the following:

  1. Go to the details of your required SLO.

  2. Unfold more options. Click Run Replay.

    replay slo
    Replaying an existing SLO on the Nobl9 Web

  3. Select the required period for data retrieval.
    The pre-selected value is the default period for historical data retrieval set for this data source.

  4. Click Run Replay.

Run Replay is inactive in the following cases:

  • Your data source is unsupported
  • The maximum period for historical data retrieval for your data source is set to 0
  • A given SLO is currently being replayed
  • Replay for a given SLO is queued

Job Status widget​

You can track the progress of ongoing replays in the Job Status widget.

To access it, click next to the top right of the Nobl9 application:

process widget
Job Status widget

Key takeaways:

  • The widget displays 3 most recent replays (the limit for concurrent replays +1).
  • All jobs are sorted by status (in progress always takes precedence) and last triggered date, with the most recent date displayed at the top.
  • You can cancel queued Replays. Once Replay is triggered, you cannot cancel its progress. The duration depends on the period configured.

Removing queued Replays from the queue​

You can remove queued Replays from the queue. For this, open the Job Status widget and click Remove under the required SLO name:

remove replay from queue
Removing Replay from the queue

As a result, Replay is no longer queued. Its status becomes canceled, and you can trigger another Replay for this SLO.

replay removed from queue
Replay removed from the queue
For a more in-depth look, consult additional resources:
ReplayReplayReplay restrictionsReplaysloctl replayReplayReplaying SLOs from other SLOsReplay
Last updated on
On this page