You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm facing a challenging issue that I'm having trouble resolving. I've installed Sloth on my Kubernetes cluster using Helm, and I've ensured that the necessary Custom Resource Definitions (CRDs) for Prometheus rules (prometheusrules.monitoring.coreos.com) and Prometheus service levels (prometheusservicelevels.sloth.slok.dev) are in place.
I've also created two examples for my Prometheus service levels (sloth-slo-my-service and sloth-slo-home-wifi). However, when I do a port forward to my Sloth pod to check these metrics related to the Prometheus service level, they aren't appearing.
Do any of you know what I might be doing wrong?
Thanks in advance for your help.
The text was updated successfully, but these errors were encountered:
PrometheusServiceLevel CRD converts into a PrometheusRule crd. Sloth pods have nothing to do with the actual metrics afaik, they are picked up by your prometheus instance instead.
Hello everyone,
I'm facing a challenging issue that I'm having trouble resolving. I've installed Sloth on my Kubernetes cluster using Helm, and I've ensured that the necessary Custom Resource Definitions (CRDs) for Prometheus rules (prometheusrules.monitoring.coreos.com) and Prometheus service levels (prometheusservicelevels.sloth.slok.dev) are in place.
I've also created two examples for my Prometheus service levels (sloth-slo-my-service and sloth-slo-home-wifi). However, when I do a port forward to my Sloth pod to check these metrics related to the Prometheus service level, they aren't appearing.
Do any of you know what I might be doing wrong?
Thanks in advance for your help.
The text was updated successfully, but these errors were encountered: