-
Task
-
Resolution: Done
-
Critical
-
None
-
5
-
False
-
-
False
-
-
-
OBSDOCS (Jan 1 - Jan 22) #247, OBSDOCS (Jan 22 - Feb 12) #248
For 4.15, the feature implemented in https://issues.redhat.com/browse/MON-1949 has added the ability to deploy an additional kubelet service monitor that adds cAdvisor metrics with the exposed timestamps. This feature improves consistency of some container metrics, at the cost of delayed staleness awareness. With https://github.com/prometheus/prometheus/pull/13060/ Prometheus can now be configured to ingest explicit timestamps but also use staleness markers for low latency stale detection.
This means that the dedicatedServiceMonitor feature will be deprecated in this release, which we need to note in the documentation in the Release Notes and by removing the https://docs.openshift.com/container-platform/4.14/monitoring/configuring-the-monitoring-stack.html#configuring-a-dedicated-service-monitor_configuring-the-monitoring-stack topics from the core platform monitoring docs.
- clones
-
MON-3452 Configure trackTimestampsStaleness for kubelet ServiceMonitor
- Closed
- is blocked by
-
OCPBUGS-23442 Syncbot conflict on prometheus v2.48.0
- Closed
- is related to
-
OBSDOCS-749 Monitoring 4.15 release notes, deprecated features
- Closed
- links to