Repository navigation
[Feature]: Create a packet loss tracer #117
Description
Is your feature request related to a problem?
- No
Problem Description:
This is a parent issue of issue #78. This issue aims to expand the current metrics landscape by adding a packet loss tracer for the internal TCP connections.
Solution:
Trace the tcp_identify_packet_loss kprobe and log relevant insights.
Insights needed:
- Packet loss
- % of total packet loss
- total size of data loss
- comparison between loss data and total transmitted data
Additional info
Testing environment: minikube single node with Chaos Mesh
Related discussion: What Metrics Should We Trace, Monitor, and Analyze with eBPF?
Metadata
Metadata
Assignees
Type
Projects
- Status
Activity
[#117]: added metrics_tracer crate (kernel space BPF program)
[#117]: added metrics crate (user space metrics collector)
[#117]: added kubernetes manifest for metrics collector service
[CortexFlow#117]: packet loss tracer working along with chaos mesh
[CortexFlow#117]: packet loss tracer working along with chaos mesh
[CortexFlow#117]: packet loss tracer working along with chaos mesh
[CortexFlow#117]: packet loss tracer working along with chaos mesh
[CortexFlow#117]: packet loss tracer working along with chaos mesh
[CortexFlow#117]: renaming fields of net_metrics
[CortexFlow#117]: Move display events for metric tracer to helpers
[CortexFlow#117]: Move display events for metric tracer to helpers