PCAPs and L4 Streams
Optimized for Performance and Scale
PCAP - Network Traces
PCAP provides all packet information from the Ethernet header all the way to the application payload, providing you with the full visibility of the application and network interaction, pre- and post-event.
PCAP file format is suitable to contains network traces that include all communication information relevant to the trace.
Distributed PCAP-based Storage
Kubeshark captures all L4 (UDP and TCP) streams and stores each L4 stream in a separate PCAP file in the root file system of each node in the cluster.
As the raw network traces do not include identity information (e.g. service names), kubeshark also keeps track of name resolution history in a JSON file that is attached to each PCAP file.
On-demand Network Traces (PCAPs)
Kubeshark provides means to export network traces on-demand in PCAP format, without any need for code instrumentation. You can use a rich filtering language to define the areas in your network you’d like to include in the trace.
For example, when I want to export all gRPC traffic between two pods when a certain token is used.
grpc and request.headers["Authorization"] == r"Token.*" and src.name == "front-end.sock-shop" and dst.name == "catalogue.sock-shop"
The resulting network trace will include all L4 streams that match the query, all the way to the ethernet packets.
Kubeshark enables you to manually export a network snapshot or conditionally generate and upload a network snapshot to an immutable datastore.
Manual PCAP Export
Clicking the PCAP button will download the compressed PCAP repository in a
The PCAP repository will also include one file named:
name_resolution_history.json per each node in the cluster.
name_resolution_history.json file contains the historical changes in the mapping of IPs to pod or service names:
The example below shows how to export a network snapshot of the past 72 hours:
Network Snapshot Automation
You can write custom-logic scripts to generate network snapshots based on programmatic decisions and then export the generated PCAP repositories to S3.
Read more in the Cloud Forensics section.
View the PCAP Snapshot
Kubeshark provides a CLI option to view a previously exported PCAP file.
kubeshark tap --pcap <pcap-snapshot.tar.gz>
Running the above command will open the Kubeshark dashboard in your browser and display the content of the PCAP file.
TIP: You can view the service dependency map of a previously stored PCAP file.
OSI L4 (TCP/UDP) Streams
Kubeshark stores the dissected protocols’ complete TCP or UDP streams. TCP and UDP streams include all of the request-response pairs throughout the communication between client and server.
NOTE: Captured TCP or UDP streams that do not belong to a dissected protocols are discarded
L4 Stream Section
This L4 stream section exposes the following information:
- The unique identifier of the L4 stream (internal to Kubeshark)
- The index of the item in the L4 stream
- The node name or IP.
- To open the L4 stream replay prompt.
- PCAP download (The original PCAP file of this TCP stream)
L4 Stream Replay
Use the Replay button to replay the L4 stream. Replaying a TCP or UDP stream establishes a brand new connection to the destination server using the destination IP and port of the item. It only replays the payload of client packets.
Kubeshark provides an option to replay the TCP or UDP stream concurrently. This capability is intended to provide an easy way to stress test the target server.
To activate the stress test, put any number in the replay count and select the Replay the TCP/UDP streams concurrently. (load testing).
L4 Stream Traffic Entries
When you select a traffic entry from the left-pane, all the other traffic entries that belong to the same stream are marked with dashed borders:
To automatically build such a filter that matches to items from a specific TCP or UDP stream, use the green + button by the TCP or UDP stream identifier: