Slo Spec
Definition
Optional description of the SLO, up to 1050 characters.
The service this SLO is associated with. A / separates the service namespace from the service name, so payments/eu resolves to namespace payments and name eu, and a value without a slash is just the service name. If a service name itself contains a /, prefix the value with a leading / to treat the rest as a literal name with no namespace; for example /payments/eu resolves to the name payments/eu. If nothing matches, the SLO is simply not linked to a service.
Inline Service Level Indicator (SLI). An inline indicator is required (indicatorRef is not currently supported).
Name of an external SLI. Not currently supported — provide an inline indicator instead. Requests that set indicatorRef are rejected with a 400.
Optional. A single rolling time window with a 4w (28d) duration. Only rolling 4w/28d windows are currently supported; calendar-aligned windows and other durations are rejected with a 400. When omitted, a rolling 28d window is used. Note the evaluation window is currently fixed at 28d regardless of the value provided.
Only Occurrences is currently supported. Timeslices and RatioTimeslices are not currently supported and requests using them are rejected with a 400.
"Occurrences""Timeslices""RatioTimeslices"Thresholds for the SLO. Exactly one objective is supported; multiple or composite objectives are not currently supported and requests declaring more than one objective are rejected with a 400.
Alert policies for this SLO, following the OpenSLO v1 specification. Not supported by Dash0. This field is accepted for OpenSLO compatibility, but any alert policies are ignored: they are not stored, not evaluated, and not returned when reading the SLO back.
Used by 1
These schemas and endpoints reference this type directly.