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

Closed
cih9088 opened this issue Jul 15, 2018 · 8 comments
Closed

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.)

@nicolargo
Copy link
Owner

nicolargo commented Oct 6, 2024

Hi @cih9088 / @jeffkeller87

on the develop branch, a first implementation of the feature you request 2 years ago...

Configuration:

[serverlist]
# Define columns (comma separated list of <plugin>:<field>:(<key>)) to grab/display
# Default is: system:hr_name,load:min5,cpu:total,mem:percent
# You can also add stats with key, like sensors:value:Ambient (key is case sensitive)
columns=system:hr_name,load:min5,cpu:total,mem:percent,memswap:percent:sensors:value:Ambient 

Result:

image

Can you test it on your side ?

@jeffkeller87
Copy link

In the simple case where I add a single sensor value to the [serverlist] config section, this works well. Note that there is a typo in your example configuration. This is what I used:

[serverlist]
# comma instead of colon between percent and sensors
columns=system:hr_name,load:min5,cpu:total,mem:percent,memswap:percent,sensors:value:Tctl

I was expecting to be able to add multiple sensor values, but this does not work:

[serverlist]
columns=system:hr_name,load:min5,cpu:total,mem:percent,memswap:percent,sensors:value:Tctl,sensors:value:Composite

Only a single SENSORS column shows in the central client view with values for the second configuration (Composite). It would be nice if they were both displayed, differentiated with the sensor label in the central client view. E.g., SENSORS.TCTL and SENSORS.COMPOSITE.

This gets particularly confusing when you try this where one or more sensors is not present on one or more servers. The SENSORS column gets filled with the last non-missing value. In this screenshot, the battery percentage from one server (BAT BAT0) is shown in the same column as CPU control temperature (Tctl).

Screenshot from 2024-10-06 11-10-34

@nicolargo
Copy link
Owner

@jeffkeller87 ok, feature with multiple keys on a same plugin is implemented in the develop branch.

image

@jeffkeller87
Copy link

Looks great! I will try to test this weekend.

@jeffkeller87
Copy link

jeffkeller87 commented Oct 20, 2024

@nicolargo I found a labeling issue in the central client display when a sensor label contains an underscore. The iwlwifi_1 0 sensor is displayed as 1 0 (see image). But otherwise, it is working as I expected. Thanks for adding this feature!

image

@nicolargo
Copy link
Owner

Thanks @jeffkeller87 i will correct the issue in the last version.

Thanks for all your remarks regarding the feature.

See you.

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