Nobl9 application (1.192.0)
- Clearer Replay and adjustment elapsed time
- Expanded Test metric support
- Faster processing for large Replay backfills
Release details
new Replay events in SLO Change History
Replay activity now appears in the SLO Change History. You can see when a Replay was requested, started, completed, canceled, extended, deleted, or failed.
These entries include the user or system actor behind the change, the tool used to request it, and the Replay state transition. This makes it easier to understand why an SLO's error budget changed after historical data was reprocessed.
improved Clearer Replay and adjustment elapsed time
The Replay and adjustment job status now measures Elapsed time from the moment processing starts, instead of including time spent waiting in the queue.
This makes the job status widget easier to interpret during busy periods. The same timing behavior is also reflected in Replay list data used by sloctl replay list.
improved Expanded Test metric support
Test metric now supports more data sources. With Nobl9 agent 0.114.0-beta or later, you can preview raw SLI data for the following:
- Amazon Prometheus
- Azure Monitor managed service for Prometheus
- Elasticsearch
- Google Cloud Monitoring
- LogicMonitor
- Prometheus
- ThousandEyes
improved Faster processing for large Replay backfills
Large batches of queued Replays now start at a steadier rate. Previously, a very large Replay backlog could slow down queue processing, leaving available concurrent Replay slots unused and extending the total backfill time.
The queue now scales better when many Replays are waiting, so large historical data backfills can keep moving more consistently.