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

Feature request: make the central client UI configurable (example: GPU status) #1289

Open
cih9088 opened this issue Jul 15, 2018 · 2 comments

Comments

@cih9088
Copy link

cih9088 commented Jul 15, 2018

central client feature in glances is very useful for me, I guess not only me, to monitor several servers at one go.
However it would be much useful if there were any options to show how many GPUs are not running or status of each GPUs for machine learning researchers or engineers.
As far as I know, no options for central client for now that is no way to customising it.
Thought?

@cih9088 cih9088 changed the title feature request: gnu status in central client feature request: GPU status in central client Jul 15, 2018
@nicolargo
Copy link
Owner

Hi @cih9088 !

For the moment, only majors stats (CPU/RAM) are available in the client central view. Your proposal to make it "configurable" is very interesting. Have to find a way to make it nice, not only for GPU.

If you have some requirements please let me know.

Nicolas

@nicolargo nicolargo changed the title feature request: GPU status in central client Feature request: make the central client UI configurable (example: GPU status) Jul 22, 2018
@nicolargo nicolargo added this to the Glances 4.0 milestone Nov 16, 2019
@jeffkeller87
Copy link

For me, I would like to be able to see temperature in the client central view. This stat (and others) is tricky because there could be more than one sensor for a given host and different hosts may have different sensor labels (e.g., Tctl, Tdie, Composite, etc.)

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

No branches or pull requests

3 participants