Shared agentsAlerts
Real-time and scheduled, built for scale.
- Reliability & Incident Management
//SLOs
SLOs and error budgets.Alert on burn rate, not noise.
Define what working means, measure it continuously, and alert on how fast you're burning error budget, on the engine that holds your logs, metrics, and traces.
Objectives
Measure what you promised
Define good as a query, pick a target, and get an error budget for the difference.
Burn rate
Alert on speed, not noise
Burn-rate alerts fire on sustained damage and ignore the two-minute spike.
Unified
One engine, not three tools
SLOs run on the backend already holding your logs, metrics, and traces.
//Overview
What is a service level objective (SLO)?
A service level objective (SLO) is a target for how reliably a service should work, such as 99.9% of requests succeeding over 30 days. The gap between the target and perfection is the error budget, and burn rate is how fast it is being spent.
DataObserve Sense defines SLIs as queries over your logs, metrics and traces, supports count and time-slice SLIs, and alerts on multi-window burn rate using the Google SRE workbook method, on the same engine that holds your telemetry.
//Alert on what users feel
Define good, then watch the budget
Good is a query
A scope filter, a good-when predicate, and a live preview splitting good from bad.
Count and time-slice SLIs
Success rates, latency and freshness, over rolling 7, 30, or 90 days.
Two windows
The long window proves it's real; the short one confirms it's still happening.
One series per group
Region, endpoint, or tenant each get their own SLI, budget, and burn rate.
Measurement and paging apart
An SLO only measures. Alerting on it is an ordinary alert.
Three urgencies, one objective
Fast burn pages, mid burn notifies, slow burn files a ticket.
//Explore more withDataObserve
More from Sense · Reliability & Incident Management
Incidents
Logs, metrics, and traces correlated the moment an incident fires, so your team triages and resolves with the full picture.
- Reliability & Incident Management
AI SRE
A 24/7 AI SRE that starts investigating the second an alert fires, so you arrive to root causes instead of raw telemetry.
- Reliability & Incident Management
AI Assistant
No SQL required, answers in seconds.
- Reliability & Incident Management
//FAQs
SLOs: questions teams ask
Can I change a target later?
Yes. Targets apply when the SLO is read, so every budget and burn rate re-derives instantly.
Is the burn-rate math standard?
Yes, the Google SRE workbook math, with the long window at twelve times the short.
Count or time-slice SLI?
Ask what should happen if traffic stops for ten minutes; the two answer differently.
What is the difference between an SLI, SLO and SLA?
An SLI is the measurement, such as the success rate. An SLO is the internal target for it. An SLA is a contract with customers that usually has a looser target and penalties.
What is burn-rate alerting?
Burn-rate alerting pages when the error budget is being spent fast enough to miss the SLO, which catches real user impact with less noise than static thresholds.
