Slo Metadata
Definition
Name of the SLO: an RFC 1123 compatible Kubernetes object name. Used as the display name when the dash0.com/display-name annotation is not set.
Resource labels. Keys prefixed with dash0.com/ are reserved for Dash0-managed
metadata (id, version, dataset, origin, source); reserved or blank keys supplied by
the caller are ignored. Use any other key for user-defined labels, which are stored
and returned on read. At most 50 user-defined labels are allowed.
Resource annotations. Keys prefixed with dash0.com/ are reserved for Dash0-managed
metadata. Some reserved keys are server-managed and ignored when supplied by the
caller (e.g. the timestamp annotations); others, like dash0.com/enabled and
dash0.com/display-name, are client-settable and honored on write — see the
individual property descriptions. dash0.com/display-name holds an optional
human-readable display name of the SLO, used instead of metadata.name when set
(blank values are treated as unset). Blank keys are ignored. Use any other key for
user-defined annotations, which are stored and returned on read. At most 50
user-defined annotations are allowed.
Used by 1
These schemas and endpoints reference this type directly.