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.

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

How to collect memory/cache bandwidth usage using cAdvisor? #2797

Closed
nfsp3k opened this issue Feb 4, 2021 · 2 comments
Closed

How to collect memory/cache bandwidth usage using cAdvisor? #2797

nfsp3k opened this issue Feb 4, 2021 · 2 comments
Assignees

Comments

@nfsp3k
Copy link

nfsp3k commented Feb 4, 2021

Hi,

I want to scrape memory/cache bandwidth usage by containers using cAdvisor on Kubernetes.
How can I do this?

My worker node has the flags cqm_mbm_total, cqm_mbm_local, and rdt_a set.
image

And resctrl is also mounted as follows.
image

However, when I try to scrape stats by using the REST API url 'xxx.xxx.xxx.xxx:8080/api/v1.3/subcontainers',
the result does not contain any metrics about memory/cache bandwidth usage.

I'm new to cAdvisor and I believe your response will be helpful to me.
My cAdvisor version is v0.30.2.

Thank you

@Creatone Creatone self-assigned this Feb 4, 2021
@Creatone
Copy link
Collaborator

Creatone commented Feb 4, 2021

The Resctrl metrics were introduced in v0.37.0. Unfortunately only for "/" container (the entire machine).
#2793 PR adds metrics per container. I hope it'll be merged soon. Can you check if it's working for you?

@nfsp3k
Copy link
Author

nfsp3k commented Feb 10, 2021

The Resctrl metrics were introduced in v0.37.0. Unfortunately only for "/" container (the entire machine).
#2793 PR adds metrics per container. I hope it'll be merged soon. Can you check if it's working for you?

Thanks for your reply, @Creatone. I'm going to check the PR.

@nfsp3k nfsp3k closed this as completed Feb 10, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants