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?