Glances information widget cpu, mem fields not hideable

[mgrimace]

Hello,

I'm not sure if this is a feature request or an issue. Using the regular resources information widgets, all fields are hideable (e.g., CPU, mem, temp, etc.). However, using the glances information widget, only cputemp and uptime are hideable; whereas, CPU and MEM appear to always show by default. I'd like to be able to hide cpu and mem, and just show disk storage. Entering the value cpu: false does not work for me.

Any help would be appreciated, thank you!

[benphelps]

I noticed this as well, if @shamoon doesn't feel like messing with it, I can.

[benphelps]

I think s'ti an issue?

[mgrimace]

Thanks for looking into it! It’s not an open issue as far as I can tell - it may also be me/my searches - I have some confusion with the term ‘widgets’ used in references to glances as both a service widget and an information widget, + widgets.yaml used to configure information widgets. In this case, I mean glances as used in the top information bar, and my searches turn up both uses of glances.

As a separate feature request, being able to re-order the items in the glances information widget would be great too (e.g., present them across the top bar in the order listed in widgets.yaml). For example, enabling temp and uptime order them after disks.

Ideally, I want glances to show free space of my USB backup drive attached to my Proxmox server, beside my NAS free space which is mounted in the homepage container and shows via resources. Both resources and glances can show the Proxmox server CPU, mem, uptime, and temp, but it screws up the labeling for the drives depending whether I have resources or glances show that data (if that makes sense).

Or just be able to label individual drives vs clusters.

A few options, but I can’t seem to solve myself, and I appreciate you looking at it!

[shamoon]

as noted elsewhere, ordering is not a small task and totally separate.

disabling cpu + mem was never implemented, its not in the docs or anything. But its pretty straightforward, I can take care of that

[shamoon]

Closed by #1931

[github-actions[bot]]

This discussion has been automatically locked since there has not been any recent activity after it was closed. Please open a new discussion for related concerns.