mirror of
https://github.com/openshift/openshift-docs.git
synced 2026-02-06 06:46:26 +01:00
Merge pull request #100039 from eromanova97/OBSDOCS-2025
Monitoring release notes for OCP 4.20
This commit is contained in:
@@ -564,9 +564,40 @@ On clusters that manage machines with the Cluster API, you can specify additiona
|
||||
|
||||
You can now configure a delay before the cluster autoscaler recognizes newly pending pods and schedules the pods to a new node by using the `spec.scaleUp.newPodScaleUpDelay` parameter in the `ClusterAutoscaler` CR. If the node remains unscheduled after the delay, the cluster autoscaler can scale up a new node. This delay gives the cluster autoscaler additional time to locate an appropriate node or it can wait for space on an existing pod to become available. For more information, see xref:../machine_management/applying-autoscaling.adoc#configuring-clusterautoscaler_applying-autoscaling[Configuring the cluster autoscaler].
|
||||
|
||||
[id="ocp-release-notes-monitoring_{context}"]
|
||||
[id="ocp-4-20-release-notes-monitoring_{context}"]
|
||||
=== Monitoring
|
||||
|
||||
The in-cluster monitoring stack for this release includes the following new and modified features:
|
||||
|
||||
[id="ocp-4-20-monitoring-updates-to-monitoring-stack-components-and-dependencies"]
|
||||
==== Updates to monitoring stack components and dependencies
|
||||
|
||||
This release includes the following version updates for in-cluster monitoring stack components and dependencies:
|
||||
|
||||
* Prometheus to 3.5.0
|
||||
* Prometheus Operator to 0.85.0
|
||||
* Metrics Server to 0.8.0
|
||||
* Thanos to 0.39.2
|
||||
* kube-state-metrics agent to 2.16.0
|
||||
* prom-label-proxy to 0.12.0
|
||||
|
||||
[id="ocp-4-20-monitoring-changes-to-alerting-rules"]
|
||||
==== Changes to alerting rules
|
||||
|
||||
[NOTE]
|
||||
====
|
||||
Red{nbsp}Hat does not guarantee backward compatibility for recording rules or alerting rules.
|
||||
====
|
||||
|
||||
* The expression for the `AlertmanagerClusterFailedToSendAlerts` alert has changed. The alert now evaluates the rate over a longer time period, from `5m` to `15m`.
|
||||
|
||||
[id="ocp-4-20-monitoring-support-log-verbosity-for-metrics-server"]
|
||||
==== Support log verbosity configuration for Metrics Server
|
||||
|
||||
With this release, you can configure log verbosity for Metrics Server. You can set a numeric verbosity level to control the amount of logged information, where higher numbers increase the logging detail.
|
||||
|
||||
For more information, see xref:../observability/monitoring/configuring-core-platform-monitoring/storing-and-recording-data.adoc#setting-log-levels-for-monitoring-components_storing-and-recording-data[Setting log levels for monitoring components].
|
||||
|
||||
[id="ocp-release-notes-networking_{context}"]
|
||||
=== Networking
|
||||
|
||||
|
||||
Reference in New Issue
Block a user