Skip to content

OSDOCS-2095: Added release note for descheduler metrics #31583

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Apr 21, 2021
Merged

OSDOCS-2095: Added release note for descheduler metrics #31583

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 9 additions & 0 deletions release_notes/ocp-4-8-release-notes.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -85,6 +85,15 @@ This release adds improvements related to the following components and concepts.
[id="ocp-4-8-nodes"]
=== Nodes

[id="ocp-4-8-nodes-descheduler-metrics"]
==== Prometheus metrics for the descheduler

You can now enable Prometheus metrics for the descheduler by adding the `openshift.io/cluster-monitoring=true` label to the `openshift-kube-descheduler-operator` namespace where you installed the descheduler.

The following descheduler metrics are available:

* `descheduler_build_info` - Provides build information about the descheduler.
Copy link

@kasturinarra kasturinarra Apr 15, 2021

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@bergerhoffer not sure if the description for this is apt, as below is the info we see on prometheus for the descheduler_build_info, which does not contain anything about descheduler build information.

descheduler_build_info{GoVersion="go1.16.1", endpoint="https", instance="10.129.3.143:10258", job="metrics", namespace="openshift-kube-descheduler-operator", pod="cluster-6c89d56fdd-5qzrq", service="metrics"}

Copy link
Member

@ingvagabund ingvagabund Apr 15, 2021

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It depends on how the descheduler operand was actually built. Checking https://github.com/openshift/descheduler/blob/master/images/descheduler/Dockerfile.rhel7#L4 we don't set the right LDFLAGS. Lemme fix that. Though, the description is still valid.

Copy link
Member

@ingvagabund ingvagabund Apr 15, 2021

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

openshift/descheduler#59

@kasturinarra thanks for noticing that.

* `descheduler_pods_evicted` - Provides the number of pods that have been evicted for each combination of strategy, namespace, and result. There must be at least one evicted pod for this metric to appear.

[id="ocp-4-8-logging"]
=== Cluster logging
Expand Down