Anand 0e5f506a78 Fix node RRD memory/swap/disk decoding to 0 ...

PVE's node rrddata uses a different column schema than guest (qemu/lxc)
rrddata for the same stats: memtotal/memused instead of maxmem/mem,
swaptotal/swapused instead of maxswap/swap, roottotal/rootused instead of
maxdisk/disk. decodeRRDPoints only ever looked for the guest names, so on
node rows mem/swap/disk silently decoded to zero and fell into Extra unused
— this is why the Custom Dashboard's Fleet Trend memory chart (which pulls
node rrddata) was stuck at 0B. Node RRD fetches now alias those columns
onto the same typed fields guest RRD already uses.

2026-09-03 15:58:47 +05:30

..

backup.go

Initial commit

2026-09-03 08:36:04 +05:30

client.go

Initial commit

2026-09-03 08:36:04 +05:30

datacenter.go

Initial commit

2026-09-03 08:36:04 +05:30

firewall.go

Initial commit

2026-09-03 08:36:04 +05:30

guests.go

Initial commit

2026-09-03 08:36:04 +05:30

ha.go

Initial commit

2026-09-03 08:36:04 +05:30

nodes_test.go

Initial commit

2026-09-03 08:36:04 +05:30

nodes.go

Initial commit

2026-09-03 08:36:04 +05:30

pools.go

Initial commit

2026-09-03 08:36:04 +05:30

replication.go

Initial commit

2026-09-03 08:36:04 +05:30

rrd_test.go

Fix node RRD memory/swap/disk decoding to 0

2026-09-03 15:58:47 +05:30

rrd.go

Fix node RRD memory/swap/disk decoding to 0

2026-09-03 15:58:47 +05:30

storage.go

Initial commit

2026-09-03 08:36:04 +05:30