Nobl9 announced Replay, providing new capabilities to its Service Level Objective (SLO) platform that significantly increase and optimize how enterprises can deploy, use and benefit from SLOs.

The new features allow customers to create SLOs with historical data from the last 30 days and pre-calculates error budgets.

“Our customers run mission-critical platforms that let enterprise developers quickly deliver software applications. Nobl9 makes the handshake-agreement between platform teams and application teams explicit in code,” said Brian Singer, co-founder and CPO at Nobl9. “Now with Replay, our customers can ask ‘what if we had set different goals for our service?’ and see the results based on accurate past data so they don’t have to guess or wait for new data to accumulate.”

With Replay, customers can instantly view their last 30 days of reliability data in context when they create their SLOs. Their historical Service Level Indicator (SLI) data will be retrieved alongside real time observability metrics and merged together to see an error budget within the time window they select.

Some roadblocks for customers starting with SLOs are knowing how they did previously and what their realistic expectations should be for reliability. Replay provides a window into that by retrieving and graphing their reliability up to 30 days before the creation of the SLO. Customers can then immediately see if their historical data met the reliability criteria they set and see what error budget is remaining once their SLO is created.

Instead of exporting data and reviewing the last 30 days of metrics in a spreadsheet, with Replay, Nobl9 enables automation to capture historical data, merge them with real time SLI data, and allows customers to view SLO charts and generate reports shortly after creating an SLO.

Replay supports Datadog, Prometheus, Amazon Managed Prometheus, Splunk, and Graphite metrics. Additional data sources will be added soon.

Replay is now available in beta to all existing Nobl9 customers.