devloperdevesh / devloperdevesh/FaultPlane
research(ebpf): prototype Linux eBPF ingress telemetry integration
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 2
- Forks
- 1
- Avg merge
- 14m
- Merged PRs (30d)
- 57
Description
Overview
Explore adding an experimental Linux eBPF-based telemetry layer for FaultPlane.
The current runtime collects connection information from user-space components.
This research task investigates whether kernel-level networking signals can improve runtime visibility and failure detection.
Proposed Work
Implement an experimental eBPF integration:
- Add an eBPF prototype under
experimental/ebpf/ - Create a minimal C-based eBPF program
- Add a Go loader using
github.com/cilium/ebpf - Document supported Linux kernel requirements
- Keep the feature isolated from the stable runtime
Expected Outcome
A working prototype capable of:
- Attaching an eBPF program
- Receiving kernel networking events
- Exporting events into FaultPlane telemetry
Scope
This is a research feature.
The goal is not to replace the current gateway implementation, but to evaluate future kernel-level observability capabilities.
References
Related areas:
- Linux eBPF
- XDP
- Kernel networking telemetry
- cilium/ebpf
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 in experimental/ebpf/ and review the cilium/ebpf integration approach, along with the current user-space connection telemetry. Define the minimal C eBPF program and Go loader while keeping them isolated from the stable runtime. Done means the prototype attaches, receives kernel networking events, exports them into FaultPlane telemetry, and documents supported Linux kernel requirements.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c, go, linux
- Domain
- networking, observability, operating-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100