Skip to content
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

Jump to bottom

[BUG] Wrong metric expression for Deployment/ReplicaSet Metric's section #44726

Closed
MKlimuszka opened this issue Mar 7, 2024 · 1 comment
Closed

[BUG] Wrong metric expression for Deployment/ReplicaSet Metric's section #44726

MKlimuszka opened this issue Mar 7, 2024 · 1 comment
Labels
area/monitoring internal kind/bug Issues that are defects reported by users or that we know have reached a real release team/observability&backup the team that is responsible for monitoring/logging and BRO

Comments

@MKlimuszka
Copy link
Collaborator

Rancher Server Setup
Rancher version: 2.7.9
Number of nodes: 3
Node OS version: Ubunutu 20.04 LTS

Monitoring version:

102.0.2+up40.1.2

Issue
This happens for any deployment/ReplicaSet in the whole cluster.

In the RancherUI, the CPU and memory metrics in the Metrics tab of any Deployment/Replicaset are wrong. They display double the amount of the actual usage.

Business impact:
Metrics are misleading.

Other
SURE-7237
@MKlimuszka MKlimuszka added area/monitoring internal kind/bug Issues that are defects reported by users or that we know have reached a real release team/observability&backup the team that is responsible for monitoring/logging and BRO labels Mar 7, 2024
This was referenced Apr 18, 2024
Closed
Closed
@MKlimuszka MKlimuszka mentioned this issue May 2, 2024
Closed
@MKlimuszka MKlimuszka added this to the v2.9-Next1 milestone May 2, 2024
@MKlimuszka MKlimuszka mentioned this issue May 3, 2024
Closed
@MKlimuszka
Copy link
Collaborator Author

Duplicate of #24343

@MKlimuszka MKlimuszka marked this as a duplicate of #24343 May 7, 2024
@MKlimuszka MKlimuszka removed this from the v2.9-Next1 milestone May 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area/monitoring internal kind/bug Issues that are defects reported by users or that we know have reached a real release team/observability&backup the team that is responsible for monitoring/logging and BRO
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@MKlimuszka