prometheus / prometheus/node_exporter
feat: optional disabled by default collector for /proc/vmallocinfo to make bpf jit usage observable
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 13.8k
- Forks
- 2.7k
- Avg merge
- 1d 23h
- Merged PRs (30d)
- 8
Description
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.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the /proc/vmallocinfo input and reproduce the documented grep/awk command to understand the BPF JIT value being measured. Done means an optional, disabled-by-default collector exposes this usage so it can be observed and used for alerting.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, linux
- Domain
- observability, operating-systems
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100