OPopenobserve
SLOs

Preview the uptime an alert would produce as an SLI source

Returns the ledger intervals for the ribbon plus the achieved SLI and the coverage behind it — the alert analogue of the time-slice preview. Computed by the same fold the ingest pass runs, so the preview cannot disagree with the SLO it is previewing.

get/api/v2/{org_id}/alerts/{alert_id}/slo-preview

Request

Path parameters

org_idstring required

Organization identifier

alert_idstring required

Source alert identifier

Query parameters

window_secsinteger required

Rolling window in seconds

slice_interval_secsinteger required

Slice width in seconds

Response

Success

alert_idstring required
coveragenumber double required

observed / expected, 0..1 — the denominator behind the SLI, which is the number that decides whether the SLO would freeze.

expected_slicesinteger required
good_secsnumber double required
observed_slicesinteger required
range_end_secsinteger required
range_start_secsinteger required

The range the ribbon is drawn against. Intervals alone cannot place a band, and a gap at either edge would otherwise be invisible.

slinumber double nullable

Percentage 0..100 over MEASURED time. None when nothing was measured — deliberately not 0, which would render a brand-new source as total downtime.

slice_interval_secsinteger required
total_secsnumber double required
would_freezeboolean required

Whether an SLO on this source would be FROZEN right now rather than reporting the SLI beside it.

[Self::sli] is the honest ratio over measured time, which is what the form asks for — but below ZO_SLO_MIN_COVERAGE the saved SLO reports no data at all (SloStatusView::derive), so "100% over 33% of the window" is a reading the SLO will refuse to give. The floor is server-side config the form cannot see, so the comparison has to travel with the answer (§2, D34).

Changes

No recorded changes to this operation across all 1 revision of this API.