Description of problem: Due to recent enabling of Prometheus own alerts for user workload prometheus some of them start firing after user workload monitoring is enabled and no samples are ingested by prometheus. > Prometheus openshift-user-workload-monitoring/prometheus-user-workload-0 is not ingesting samples. Version-Release number of selected component (if applicable): 4.5 onwards Expected results: No alerts firing when enabling user workload monitoring.
issue is fixed 4.7.0-0.nightly-2020-12-13-202314, enabled UserWorkload, there is not PrometheusNotIngestingSamples alert # oc -n openshift-monitoring get cm cluster-monitoring-config -oyaml apiVersion: v1 data: config.yaml: | enableUserWorkload: true kind: ConfigMap metadata: name: cluster-monitoring-config namespace: openshift-monitoring # token=`oc sa get-token prometheus-k8s -n openshift-monitoring` # oc -n openshift-monitoring exec -c prometheus prometheus-k8s-0 -- curl -k -H "Authorization: Bearer $token" 'https://prometheus-k8s.openshift-monitoring.svc:9091/api/v1/alerts' | jq '.data.alerts[].labels | {alertname}' { "alertname": "AlertmanagerReceiversNotConfigured" } { "alertname": "Watchdog" }
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Moderate: OpenShift Container Platform 4.7.0 security, bug fix, and enhancement update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2020:5633
*** Bug 2078667 has been marked as a duplicate of this bug. ***