-
Bug
-
Resolution: Done-Errata
-
Major
-
premerge
-
None
-
Low
-
No
-
MON Sprint 246
-
1
-
False
-
-
N/A
-
Release Note Not Required
Description of problem:
tested https://github.com/openshift/cluster-monitoring-operator/pull/2187 with PR
launch 4.15,openshift/cluster-monitoring-operator#2187 aws
don't find "scrape.timestamp-tolerance" setting in prometheus and prometheus pod, no result for below commands
$ oc -n openshift-monitoring get prometheus k8s -oyaml | grep -i "scrape.timestamp-tolerance" $ oc -n openshift-monitoring get pod prometheus-k8s-0 -oyaml | grep -i "scrape.timestamp-tolerance" $ oc -n openshift-monitoring get sts prometheus-k8s -oyaml | grep -i "scrape.timestamp-tolerance"
not in prometheus configuration file either
$ oc -n openshift-monitoring exec -c prometheus prometheus-k8s-0 -- cat /etc/prometheus/config_out/prometheus.env.yaml | head
global:
evaluation_interval: 30s
scrape_interval: 30s
external_labels:
prometheus: openshift-monitoring/k8s
prometheus_replica: prometheus-k8s-0
rule_files:
- /etc/prometheus/rules/prometheus-k8s-rulefiles-0/*.yaml
scrape_configs:
- job_name: serviceMonitor/openshift-apiserver-operator/openshift-apiserver-operator/0
- is cloned by
-
-
- Closed
-
- is depended on by
-
-
- Closed
-
- is duplicated by
-
-
- Closed
-
- links to
-
RHEA-2024:0041
OpenShift Container Platform 4.16.z bug fix update
