Step 3: Leverage your historical data

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

See how to leverage your Replay SLO.

Once you’ve completed the SLO configuration and saved your SLO, you’ll be able to see your SLI and error budget charts integrating the historical data for the specified period within a few minutes.

Use cases for Replay

You can use Replay to pull in metrics data from the past for (1) newly created SLOs or (2) for existing SLOs.

Replay may be useful when:

• Your SLO is configured incorrectly. Most often, queries return incorrect data when SLO’s data collection method is set to incremental while its SLI data is in fact non-incremental. In such case, edit your SLOand reimport historical data to ensure your error budget calculations are correct
• There were network issues with a data source and the Nobl9 agent couldn't collect data points for a prolonged time. Once the issue is resolved, you can run a reimport of the historical data to fetch data points missed by the Nobl9 agent during the outage
• You're creating a new SLO in Nobl9, but you want it to be filled at once with the historical data to monitor the performance of your service. Configure Replay for your data source, create an SLO, and run Replay for it.
• You're processing the migration of your observability tooling. Replay for new SLOs allows you to accelerate migration to Amazon Managed Service for Prometheus by honing critical SLOs in minutes, not months

Amazing! Now, leverage your Replay SLO!