send size much more than aws stats
Open
- Dominant language
- C
- Stars
- 22.7k
- Forks
- 4.1k
- Avg merge
- 10d 4h
- Merged PRs (30d)
- 3
Description
I use libbpf-toos/tcptop.bpf.c to analysis all tcp send/revc traffics. And I have a summary only with the send values among all k8s node.
1. 15TB/d by ebpf tools
2. 10TB/d by aws cost explorer
so data by ebpf shoud't larger than aws, right?
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reviewing libbpf-toos/tcptop.bpf.c and how it calculates and aggregates send values across Kubernetes nodes. Compare that result with the AWS Cost Explorer total described in the issue, and reproduce the discrepancy. Done means the difference is explained or the calculation is corrected and verified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, c, kubernetes, linux
- Domain
- cloud, networking, observability-sre
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 28/100