iovisor/bcc

Application stack trace on oomkill.

Open

#3,654 opened on Oct 11, 2021

View on GitHub
 (7 comments) (0 reactions) (0 assignees)C (4,065 forks)batch import
enhancementgood first issuenew option

Repository metrics

Stars
 (22,620 stars)
PR merge metrics
 (Avg merge 12d 6h) (12 merged PRs in 30d)

Description

Is it possible to get an application level stack trace on oomkill? Are there any examples of how I might write a script to do something like that?

Contributor guide

Research direction
Look into BPF tools in bcc for tracing OOM killer events. Check existing tools like 'oomkill' in bcc/tools/ for examples. Understand how to attach a BPF program to trace kill() or similar functions to capture process stack traces on OOM.
Tech stack
c
Domain
observabilityinfrastructure
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
Linux
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40