Slo Labels
Definition
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.
Unique internal ID of the SLO. Set by the server on creation; do not set manually.
External identifier for API-managed resources (e.g. the CRD name from an operator or Terraform resource ID). Empty for user-created SLOs; non-empty for SLOs created via the internal API. SLOs with a non-empty origin have write access controlled exclusively through explicit permission entries rather than by the admin role.
Current version of the SLO. Needs to be set when updating an SLO to prevent conflicting writes.
Dataset this SLO belongs to. Defaults to the default dataset when absent.
Origin of a Dash0 resource, derived from dash0.com/origin on read.
ui: created interactively in the Dash0 UI.terraform: managed via the Dash0 Terraform provider.operator: managed via the Dash0 Kubernetes operator.dash0-cli: managed via the Dash0 CLI.platform: owned by Dash0 rather than by anyone in your organization. Covers both resources Dash0 generates from another resource you own (the recording rules an SLO produces) and resources Dash0 ships with the product (the built-in views).api: created directly through the API, and the fallback for any origin whose prefix is not recognized.
New values may be added over time. Treat an unrecognized value as api
rather than rejecting the response.
"ui""terraform""operator""dash0-cli""platform""api"Additional properties
Used by 1
These schemas and endpoints reference this type directly.