Skip to main content

Replaying SLOs

Reading time: 0 minute(s) (0 words)

You can replay SLOs in two ways:

note

Composite SLOs support both ways, with some differences. See Replaying composite SLOs.

When an SLO is replayed on creation, it may temporarily show a No data status because retrieving and processing historical data takes time. Once the process is complete, your SLO will display the reliability values and charts for the replayed period.

When you replay an existing SLO, its charts and reliability values continue to show calculations from before the Replay was triggered. Once the new data is retrieved and processed, the SLO's charts and values are updated.

The Job Status widget allows you to:

This functionality is also available with sloctl.

Replaying SLOs on creation​

To include historical data in your new SLO, set Replay during SLO creation. This option is available for supported data sources, and if your data source has a maximum period for historical data retrieval set to a non-zero value. Saving the SLO automatically triggers or queues the Replay.

  1. Go to the Service Level Objectives section on the Nobl9 Web.
  2. Click .
  3. Select the required data source.
  4. Specify the required Period for historical data retrieval.
  5. Configure the query and other parameters.
  6. Click CREATE SLO.

Depending on Replay slot availability, the Replay will either start immediately or be queued.

If a Replay fails

If Replay fails, the SLO will still be created. However, error budget calculations will only begin from the moment of creation and will not include historical data.

Replaying existing SLOs​

You can replay existing SLOs at any time. This action is permanent and overwrites the existing SLI data for the selected period with newly retrieved or calculated data. Before you begin, consider the impact a Replay has on connected resources.

To replay an SLO:

  1. Go to the details page for the desired SLO.

  2. Click the More more options menu and select Run Replay.

    Replay an SLO
    Replaying an existing SLO

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

  4. Click Run Replay.

The Run Replay button is inactive if:

  • The data source is not supported.
  • The maximum period for historical data retrieval for the data source is set to 0.
  • The SLO is already being replayed.

Replaying composite SLOs​

Replaying a composite SLO is different from replaying a standard SLO because it does not import data from a data source. Instead, it recalculates the composite's reliability based on the existing historical data from its component SLOs.

You can replay composite SLOs in the same two ways as standard SLOs:

  • On creation
    This helps you get value from a new composite SLO more quickly.
    1. In the Budget step of the composite SLO wizard, select Include historical data.
    2. Specify the calculation period.
    3. Finish configuring the SLO and click Create SLO. The Replay will be queued or start immediately. Once complete, the composite SLO will display reliability values based on its components' historical data.
  • For an existing composite SLO
    This allows you to update a composite SLO after one of its components has been replayed or adjusted.
    1. On the composite SLO's details page, click More Options and select Run Replay.
    2. Specify the period for the recalculation.
    3. Click Run Replay.

Before replaying a composite SLO, review the common Replay restrictions and how Replay affects composite SLOs.

When selecting the recalculation period, check the component SLOs for data gaps. If you find any, you can either replay the components with missing data first or select a narrower period where most components have complete data.

Job Status widget​

You can track the progress of the 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
  • The widget displays the 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.
  • Elapsed time reflects real process time: it starts counting when Replay begins processing and excludes time spent in the queue. A Replay that is still queued shows the time since it was triggered instead.

Terminating Replay​

To terminate a Replay process:

  • Remove a queued Replay from the queue.
  • Cancel an ongoing standard Replay during the data import step. Active composite Replays cannot be canceled.

To do this, open the Job Status widget and click Remove or Cancel next to the SLO name.

remove replay from queue
Removing Replay from the queue

A Replay that is removed from the queue disappears from the list. A Replay can only be canceled during the data importing step. Once data import is complete, the Replay proceeds to data processing and cannot be canceled.

Both actions, like all Replay lifecycle events, are recorded in the SLO's Change history tab.

Check out these related guides and references:
ReplayReplayReplay restrictionsReplaysloctl replayReplayComposites and ReplayComposite SLOs
Last updated on
On this page