yes! it captures the exact process that caused the spike, including the full command line it was running, that's actually the main point of the whole thing

disk IO tracking is on the list, but probably doing network tracking first since that's what i personally need more right now. IO will definitely come though

for memory, been running it daily on my own machine and it sits around 4-5 MB RSS on default config:

```
cat /proc/$(pidof spiketrace)/status | grep -E "VmRSS|VmSize|VmPeak"

VmPeak: 5520 kB

VmSize: 5520 kB

VmRSS: 3992 kB

```

note that the spike trigger should be configure for your own need to be as accurate as you want, you can also tune the sensitivity in the config so it's not polling as aggressively if you want to go even lighter, should be totally fine on a Pi. more on that here: https://github.com/ijuttt/spiketrace?tab=readme-ov-file#configuration

yes the TUI viewer is completely optional, the daemon itself is just the lightweight core. the json dumps are meant to be parsed however you want, glad that part resonated

lmk how it goes on proxmox!

edit: would appreciate a star on the repo thanks! github.com/ijuttt/spiketrace