Skip to content

[kube-stack/workload-total.json] Bandwith and bytes dimensions are misleading #7173

Description

@baj3ovr

Describe the bug a clear and concise description of what the bug is.

Hello,

while analyzing some data in this board, there were numbers that didn't made sense and after digging deeper, there was this issue found regarding the containers that use "host_network". The issue is explain in google/cadvisor#2615, and maybe it would make more sense to replace the following:
on (namespace,pod) group_left(workload,workload_type) namespace_workload_pod:kube_pod_owner:relabel{cluster="$cluster",namespace=~"$namespace", workload=~"$workload", workload_type=~"$type"}) by (pod))

with

on (namespace,pod) group_left(instance) kube_pod_info{host_network="false",cluster="$cluster",namespace=~"$namespace", created_by_kind=~"$type",}) by (pod))

Hope you understand the issue and are able to fix it.

Thank you

What's your helm version?

3.17.0

What's your kubectl version?

Client Version: v1.35.3 Kustomize Version: v5.7.1 Server Version: v1.34.7

Which chart?

kube-prometheus-stack

What's the chart version?

78.5.0

What happened?

No response

What you expected to happen?

No response

How to reproduce it?

No response

Enter the changed values of values.yaml?

No response

Enter the command that you execute and failing/misfunctioning.

no command here

Anything else we need to know?

No response

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't workingchart/kube-prometheus-stackIssues related to the kube-prometheus-stack Helm Chart

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions