Live traffic tracing for pods in a network
The disclosure provides an example method for live packet tracing. Some embodiments of the method include configuring a first network interface of a first pod to mark each of a plurality of packets, with a corresponding flow tag and a corresponding packet identifier, receiving, from one or more observation points, at least one of copies or metadata of the plurality of packets each marked with the corresponding flow tag and the corresponding packet identifier. In some embodiments, the method further includes displaying data indicative of the at least one of the copies or the metadata of the plurality of packets.
1. A method for live packet tracing to allow diagnosis of network traffic at a flow level in a computer network, comprising:
configuring a first network interface of a first pod to mark each of a plurality of packets with a corresponding flow tag and a corresponding packet identifier;
receiving, from one or more observation points, at least one of copies or metadata of the plurality of packets each marked with the corresponding flow tag and the corresponding packet identifier; and
displaying data indicative of the at least one of the copies or the metadata of the plurality of packets.
2. The method of claim 1 , wherein configuring the first network interface comprises:
inserting a hook at the first network interface; and
installing a program at a node running the first pod, wherein the hook calls the program to mark a packet when the packet is received at the first network interface.
3. The method of claim 2 , wherein the program is an eBPF program.
4. The method of claim 1 , wherein the corresponding flow tag is included as a differentiated services code point (DSCP) value in each of the plurality of packets.
5. The method of claim 1 , wherein the corresponding packet identifier is included in an internet protocol identification (IPID) field in each of the plurality of packets.
6. The method of claim 1 , wherein the first network interface of the first pod is configured to mark packets transmitted to a second pod, and further comprising configuring a second network interface of the second pod to mark packets transmitted to the first pod.
7. The method of claim 6 , further comprising correlating a flow tag associated with a forward flow from the first pod to the second pod with a flow tag associated with a reverse flow from the second pod to the first pod.
8. A system for live packet tracing to allow diagnosis of network traffic at a flow level in a computer network comprising:
one or more processors; and
at least one memory, the one or more processors and the at least one memory configured to:
configure a first network interface of a first pod to mark each of a plurality of packets with a corresponding flow tag and a corresponding packet identifier;
receive, from one or more observation points, at least one of copies or metadata of the plurality of packets each marked with the corresponding flow tag and the corresponding packet identifier; and
display data indicative of the at least one of the copies or the metadata of the plurality of packets.
9. The system of claim 8 , wherein the one or more processors and the at least one memory are further configured to:
insert a hook at the first network interface; and
install a program at a node running the first pod, wherein the hook calls the program to mark a packet when the packet is received at the first network interface.
10. The system of claim 9 , wherein the program is an eBPF program.
11. The system of claim 8 , wherein the corresponding flow tag is included as a differentiated services code point (DSCP) value in each of the plurality of packets.
12. The system of claim 8 , wherein the corresponding packet identifier is included in an internet protocol identification (IPID) field in each of the plurality of packets.
13. The system of claim 8 , wherein the first network interface of the first pod is configured to mark packets transmitted to a second pod, and wherein the system is further configured to configure a second network interface of the second pod to mark packets transmitted to the first pod.
14. The system of claim 13 , wherein the one or more processors and the at least one memory are further configured to correlate a flow tag associated with a forward flow from the first pod to the second pod with a flow tag associated with a reverse flow from the second pod to the first pod.
15. A non-transitory computer-readable medium comprising instructions that, when executed by one or more processors of a computing system, cause the computing system to perform operations for live packet tracing to allow diagnosis of network traffic at a flow level in a computer network, the operations comprising:
configuring a first network interface of a first pod to mark each of a plurality of packets with a corresponding flow tag and a corresponding packet identifier;
receiving, from one or more observation points, at least one of copies or metadata of the plurality of packets each marked with the corresponding flow tag and the corresponding packet identifier; and
displaying data indicative of the at least one of the copies or the metadata of the plurality of packets.
16. The non-transitory computer-readable medium of claim 15 , the operations further comprising:
inserting a hook at the first network interface; and
installing a program at a node running the first pod, wherein the hook calls the program to mark a packet when the packet is received at the first network interface.
17. The non-transitory computer-readable medium of claim 15 , wherein the corresponding flow tag is included as a differentiated services code point (DSCP) value in each of the plurality of packets.
18. The non-transitory computer-readable medium of claim 15 , wherein the corresponding packet identifier is included in an internet protocol identification (IPID) field in each of the plurality of packets.
19. The non-transitory computer-readable medium of claim 15 , wherein the first network interface of the first pod is configured to mark packets transmitted to a second pod, and wherein the operations further comprise configuring a second network interface of the second pod to mark packets transmitted to the first pod.
20. The non-transitory computer-readable medium of claim 19 , the operations further comprising correlating a flow tag associated with a forward flow from the first pod to the second pod with a flow tag associated with a reverse flow from the second pod to the first pod.