Lens Metrics get wrong values of CPU, RAM

[karkill]

Describe the bug
I use the m6i.large instance (AWS), it is in the general purpose family with 2 vCPUs, 8.0 GiB RAM but in Lens I see it double (4 vCPUs, 15.265 GiB RAM)
Screenshots

Environment (please complete the following information):

• Lens Version: 2023.3.21022-latest
• OS: MACOS

[Nokel81]

Do you have multiple prometheus installations installed on this cluster?

[karkill]

I have only one prometheus installed by kube-prometheus-stack

[massimeddu-sj]

Hi have a similar problem with POD memory metric.

At pod level I see the the double of the real value, while at container level I see the right value. (The pod has just one container). See attached screenshot. I also have a Prometheus stack installed with kube-prometheus-stack.

Lens version: 2023.3.71735-latest
OS: Linux

It looks a regression with the latest version of Lens, because with older version of Lens I see the correct value.

[kyleli666]

@jweak my Prometheus is bitnami/kube-prometheus chartVesion8.3.12 appVersion0.63.0
I have POD memory metric doubled, while container memory is correct. Node metrics are also correct.
My cluster is EKS v1.24
this bug happen with all deployments
the metrics were correct in Lens Extension API v6.2.5

[andrezaycev]

+1

[saad-littera]

+1

[centromere]

These are the values being summed together:

Related code:

lens/packages/core/src/main/prometheus/operator-provider.injectable.ts.ts

Lines 79 to 80 in 4b1d740

	case "memoryUsage":
	return `sum(container_memory_working_set_bytes{pod=~"${opts.pods}", namespace="${opts.namespace}"}) by (${opts.selector})`;

The problem may have been introduced in this commit.

[Nokel81]

@centromere Thanks for this. I will add a way to specify which version to use.

[jseletz-rave]

+1 - I am seeing double the CPU and Memory requests for containers than what are actually requested.

[7wingfly]

I've noticed that it starts off with the correct metrics when the nodes are created but then suddenly doubles everything after a few minutes

[vilianvenkov]

+1

[jweak]

Hey guys, I'm unable to reproduce this issue with https://github.com/prometheus-community/helm-charts/tree/main/charts/kube-prometheus-stack installed. Could you guys share a bit more about your setup?

What kube version are you using? Which version of the kube-prometheus-stack are you using? Does this bug happen with all deployments? Are you all having both node and pod metrics doubled?

No need to post anything sensitive but some example would go a long way fixing, thanks!