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

Show only active Disk I/O (and network interface) #2929

Open
dfadev opened this issue Aug 24, 2024 · 7 comments
Open

Show only active Disk I/O (and network interface) #2929

dfadev opened this issue Aug 24, 2024 · 7 comments

Comments

@dfadev
Copy link

dfadev commented Aug 24, 2024

Is your feature request related to a problem? Please describe.
DISK I/O section takes up too much space when you have 10+ disks and each are using device mapper.

Describe the solution you'd like
A toggle key that makes the DISK I/O section only show active disks where R/s or W/s is greater than zero.

Describe alternatives you've considered
None.

Additional context
image

Copy link

This issue is available for anyone to work on. Make sure to reference this issue in your pull request. ✨ Thank you for your contribution ! ✨

@nicolargo
Copy link
Owner

@dfadev As a workaround you can hide dm and sd disk from the Glances configuration file:

[diskio]
...
hide=loop.*,/dev/loop.*,dm.*,sd.*
...

@nicolargo nicolargo added this to the Glances 4.2.0 milestone Sep 8, 2024
@nicolargo nicolargo changed the title show only active disk I/O Show only active Disk I/O (and network interface) Sep 8, 2024
@nicolargo
Copy link
Owner

Implemented in the develop branch by adding a hide_zero option.

To enable the feature:

[diskio]
...
hide_zero=True
...

@nicolargo
Copy link
Owner

@dfadev can you test the develop branch ?

@dfadev
Copy link
Author

dfadev commented Sep 8, 2024

image

"Works on my machine"

Of course now that I see it I think hide_threshold_bytes also makes sense, so the tiny 14K writes don't show up.

Would be nice to have this on network interfaces too:
image

@dfadev
Copy link
Author

dfadev commented Sep 8, 2024

Also while I'm at it, a small delay before removing it from the list could make sense. Sort of debounce the removal so if activity drops for a few seconds then picks back up the entry doesn't phase in and out.

@dfadev
Copy link
Author

dfadev commented Sep 14, 2024

I see this was implemented for network interfaces too, very cool. Here's a quick video of it in action that shows why an entry removal delay and a configurable threshold could be nice.

glances-2024-09-13_22.55.36.mp4

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

2 participants