SLI Analyzer Beta
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 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 |
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 |