aquasecurity / aquasecurity/tracee
Extract pipeline package out of ebpf package
Open
kind/chore
- Dominant language
- Go
- Stars
- 4.6k
- Forks
- 507
- Avg merge
- 2d 8h
- Merged PRs (30d)
- 9
Description
Today we have all pipeline related logic as part of the ebpf package.
Since ebpf package should handle ebpf related stuff (programs, maps, perf/ring buffers), it makes sense to extract the pipeline related logic out of it. This includes event's decoding, enrichment, processing etc.
Contributor guide
Research direction
Start by mapping the pipeline-related logic currently inside the ebpf package, including event decoding, enrichment, and processing. Done means that pipeline logic is extracted from ebpf while ebpf retains responsibility for programs, maps, and perf/ring buffers, with behavior preserved.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, linux
- Domain
- operating-systems, security
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100