When creating an SLO, I'd like to be able to group by more than one field (dimension).
Describe a specific use case for the feature:
There are use cases where it requires grouping by more than one field to achieve a proper resolution for SLOs.
An example is Kubernetes deployments:
Suppose you want an SLI that tracks if a container regularly surpasses its CPU or Memory request value. From an SLO perspective, you wouldn't be able to just use the kubernetes.container.name field, as you could have multiple pods/environments/deployments and a single group by becomes insufficient.
For an SLO like this, you'd want to be able to group by at least: kubernetes.pod.name & kubernetes.container.name, but also possibly additional dimensions for things like environment/deployment name.
Describe the feature:
When creating an SLO, I'd like to be able to group by more than one field (dimension).
Describe a specific use case for the feature:
There are use cases where it requires grouping by more than one field to achieve a proper resolution for SLOs.
An example is Kubernetes deployments:
Suppose you want an SLI that tracks if a container regularly surpasses its CPU or Memory request value. From an SLO perspective, you wouldn't be able to just use the
kubernetes.container.name
field, as you could have multiple pods/environments/deployments and a single group by becomes insufficient.For an SLO like this, you'd want to be able to group by at least:
kubernetes.pod.name
&kubernetes.container.name
, but also possibly additional dimensions for things like environment/deployment name.