microsoft / microsoft/ProcDump-for-Linux
Procdump -c does not work in k8s
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 3.1k
- Forks
- 327
- Avg merge
- 3d 10h
- Merged PRs (30d)
- 7
Description
Expected behavior
In a Kubernetes environment, when using procdump with the command 'procdump -c 10 -s 1 -w XXX', it doesn't generate a dump file when the CPU usage of the pod exceeds 10%. This might be because procdump monitors the CPU usage of the host machine instead of the pod itself. Could you consider adding monitoring for the pod's CPU and memory usage in future versions? It would greatly assist in troubleshooting .NET applications in Kubernetes.
System information (e.g., distro, kernel version, etc.)
pod docker image based on mcr.microsoft.com/dotnet/aspnet:7.0-bullseye-slim-amd64.
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 by reproducing procdump -c 10 -s 1 -w XXX in the reported Kubernetes environment using the listed .NET container image, then compare the monitored CPU usage with the pod's usage. The issue is done when CPU or memory thresholds trigger a dump for the pod rather than only reflecting host usage.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c, docker, kubernetes, linux
- Domain
- cli, devops, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100