Skip to main content

SLI Analyzer
Beta

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

To choose a meaningful reliability target for your SLO, you need to understand the performance of your system over a past period. One way to understand this is to create and adjust SLO targets every few weeks.

SLI Analyzer can be a game changer, though. It retrieves historical data collected by your data source so you can analyze your system performance using different reliability targets.

Once the analysis is complete, adjust the reliability targets and assess how the error budget and burn down rate change for your SLI. Determine your acceptable targetβ€”and you're ready to create a new SLO right from the analysis.

Leveraging SLI Analyzer, you can:

  • Create and instantly adjust SLOs in Nobl9 for more robust reliability monitoring.
  • Choose a meaningful reliability target by analyzing how your SLOs will behave, even before the SLO is created.
  • Understand the reliability of your services without waiting and adjusting them every few days or weeks.

SLI Analyzer scope of support​

Data sources SLI Analyzer supports, minimum required agent version, maximum period of historical data retrieval, and API rate limits:

Data source nameNobl9 agent minimum versionMaximum period for historical data retrieval
Amazon CloudWatch 0.65.015 days
Amazon Prometheus 0.65.030 days
AppDynamics 0.68.030 days
Azure Monitor 0.69.0-beta0130 days
Azure Monitor managed service for Prometheus 0.78.0-beta30 days
Datadog 0.65.030 days
Dynatrace 0.66.028 days
Google Cloud Monitoring 0.79.0-beta30 days
Graphite 0.65.030 days
LogicMonitor 0.81.0-beta30 days
New Relic 0.65.030 days
Prometheus 0.65.030 days
ServiceNow Cloud Observability 0.65.030 days
Splunk 0.65.030 days
Other limitations
Amazon CloudWatch: only the Configurations queries are supported.
Google Could Monitoring: the historical data retrieval period can be less for some metrics, depending on Google's data retention period.
For a more in-depth look, consult additional resources: