Using Kubernetes labels/annotation as Prometheus alert labels and annotations is limiting about pyrra HOT 4 OPEN

We could easily fix that by adding an option for adding extra labels/annotations in the Alerting spec

from pyrra.

Oh, that's an interesting point with the URLs. I haven't run into this myself yet.
I guess in that case your proposal makes sense.

The original reasoning for having them as CRD labels is to make filtering via kubectl get slo -l pyrra.dev/team=backend possible. I wonder how much usage that feature has in the first place.

from pyrra.

The original reasoning for having them as CRD labels is to make filtering via kubectl get slo -l pyrra.dev/team=backend possible. I wonder how much usage that feature has in the first place.

I usually search for SLOs using ArgoCD UI or Pyrra UI. I haven't used kubectl in a while, honestly 😬. If people rely on that feature, I guess they could keep their labels there, but I understand the duplicated effort to keep labels in sync in two different places.

I can totally understand that I don't represent all users! Do you see other people requesting the original use case?

from pyrra.

In our case, we use annotations for runbooks and dashboard links, they are also propagated when prefixed with pyrra.dev/ and allow for much larger texts. I think labels are meant to be used more to filter, which is not something we usually require for those links.

from pyrra.