Open stevo-f3 opened 1 year ago
For issues like https://github.com/awslabs/amazon-eks-ami/issues/1219 memory leak to be observable, support alerting, by exposing /proc/vmallocinfo from the node - we need an additional collector.
Current "workaround", of manually running
cat /proc/vmallocinfo | grep bpf_jit | awk '{s+=$2} END {print s}'
is suboptimal in many ways.
@SuperQ WDYT?
Seems reasonable. But parsing needs to go into procfs
For issues like https://github.com/awslabs/amazon-eks-ami/issues/1219 memory leak to be observable, support alerting, by exposing /proc/vmallocinfo from the node - we need an additional collector.
Current "workaround", of manually running
is suboptimal in many ways.