Historical data retrieval
Historical data retrieval is a tool for obtaining SLI data from the past, which is useful for SLO backfilling and data analysis. It allows you to understand your service's historical performance and make informed decisions regarding your reliability targets.
Historical data retrieval refers to the underlying process for two Nobl9 tools:
SLI Analyzer queries your data source for time series data, analyzes the data obtained, and provides metrics for SLIs. With it, you can configure your reliability objectives observing error budget changes with different targets. You can do the following:
- Create and configure analyses-based SLOs.
- Select meaningful targets by analysing SLO behavior before you create one.
- Better understand your service reliability without endless correction.
Replay offers the ability to retrieve previously collected SLI data from the data source, allowing you to:
- Restore missing or corrupted SLI data.
- Create SLOs with historical data, without waiting for data to collect naturally, over days or weeks.
- Backfill SLOs with historical data after editing critical settings like query, error budget calculation method, time window, and other.
Historical data retrieval period depends on your data source capabilities. When the period is long, historical data retrieval can consume significant resources and take time, so you may want to limit its maximum period on the integration level to prevent overload.
Setting up historical data retrieval
To make historical data retrieval possible for your required data source (if supported), configure it at the integration level when adding a data source to your Nobl9 organization.
This step is optional for the basic data source configuration. However, it's required when you need to analyze SLI data and replay SLOs.
In the data source wizard on the Nobl9 Web, under Advanced settings, do the following:
-
Set the Maximum period for historical Data Retrieval value.
It sets limits for how far back in the past Nobl9 can query data from your data source1.
In SLI Analyzer, this value is applied by default for the Graph time window. -
Specify the value for Default period for historical data retrieval.
It will be used for replaying SLOs based on your data source.
You can override this value for individual SLOs when creating them.
1Your data source, for its part, can also limit the period for historical data retrieval. This may be dictated by their data retention policy, for example. Overriding the maximum value in Nobl9, you can set additional limits to prevent overloading or regulate the duration of the data retrieval process.
Requirements:
- Both values must be the whole positive numbers or zero.
- The default period value must be up to the maximum period set for this data source.
- The maximum period must be up to the maximum period allowed initially by your data source.
Supported data sources
| Data source name | Nobl9 agent minimum version | Maximum period for historical data retrieval |
|---|---|---|
| Amazon CloudWatch | 0.65.0 | 15 days |
| Amazon Prometheus | 0.65.0 | 30 days |
| AppDynamics | 0.68.0 | 30 days |
| Azure Monitor | 0.69.0-beta01 | 30 days |
| Azure Monitor managed service for Prometheus | 0.78.0-beta | 30 days |
| Datadog | 0.65.0 | 30 days |
| Dynatrace | 0.66.0 | 28 days |
| Elasticsearch | 0.85.0-beta | 30 days |
| Google Cloud Monitoring | 0.79.0-beta | 30 days |
| Graphite | 0.65.0 | 30 days |
| LogicMonitor | 0.81.0-beta | 30 days |
| New Relic | 0.65.0 | 30 days |
| Prometheus | 0.65.0 | 30 days |
| ServiceNow Cloud Observability | 0.65.0 | 30 days |
| Splunk | 0.65.0 | 30 days |