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

response of api/metrics/v1 does not contain cpu metric #114

Open
Abdellah91 opened this issue Nov 26, 2021 · 1 comment
Open

response of api/metrics/v1 does not contain cpu metric #114

Abdellah91 opened this issue Nov 26, 2021 · 1 comment
Labels

Comments

@Abdellah91
Copy link

Abdellah91 commented Nov 26, 2021

Hello,
I installed plugin jupyter-resource-usage on a jupyterhub. the jupyterhub is deployed via helm chart on kubernetes cluster. When a request is sent to /api/metrics/v1 the response is {"rss": 112574464, "limits": {"memory": {"rss": 2147483648, "warn": false}}}. In the values.yml, of the jupyterhub helm chart config I have:
hub:
extraConfig:
firstConfig.py: |
c.ResourceUseDisplay.track_cpu_percent = True

Do you know why the cpu metric is not in the response of the api call?

@Abdellah91 Abdellah91 added the bug label Nov 26, 2021
@welcome
Copy link

welcome bot commented Nov 26, 2021

Thank you for opening your first issue in this project! Engagement like this is essential for open source projects! 🤗

If you haven't done so already, check out Jupyter's Code of Conduct. Also, please try to follow the issue template as it helps other other community members to contribute more effectively.
welcome
You can meet the other Jovyans by joining our Discourse forum. There is also an intro thread there where you can stop by and say Hi! 👋

Welcome to the Jupyter community! 🎉

@Abdellah91 Abdellah91 changed the title response of api/metrics/v1 does not contain cpu metrics response of api/metrics/v1 does not contain cpu metric Nov 26, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant