network-observability-cli is a lightweight Flow, Packet and Metrics visualization tool.
It deploys NetObserv eBPF agent on your k8s cluster to collect flows or packets from nodes network interfaces
and streams data to a local collector for analysis and visualization.
Output files are generated under output/flow and output/pcap directories per host name.
On Openshift environments, you can also capture metrics in your monitoring stack and display a fully configured dashboard.
To run this CLI, you will need:
- A running kubernetes / OpenShift cluster
- either
ocorkubectlcommand installed and connected to your cluster - Cluster admin rights
The CLI is available as a Krew plugin, which is the fastest way to get it up and running if you already use Krew. If not, please refer to its installation guide.
To install the NetObserv CLI, run:
kubectl krew install netobservOr if you had an older version, to update it:
kubectl krew update netobservThen, run it as a kubectl plugin, such as:
kubectl netobserv --version
# output example:
# Netobserv CLI version v0.0.8You can get detailed help using these commands:
kubectl netobserv --help
kubectl netobserv flows --help
kubectl netobserv packets --help
kubectl netobserv metrics --helpFor instance, to capture all flows on the cluster that go through the br-ex network interface:
-
As a
kubectlplugin:kubectl netobserv flows --interfaces=br-ex
-
Or from the repository
Makefile:Run the following command to start capturing flows, replacing
USER,VERSIONandCOMMAND_ARGSaccordingly:USER=netobserv VERSION=dev COMMAND_ARGS=--interfaces=br-ex make flows
It will display a table view with latest flows collected and write data under output/flow directory. To stop capturing press Ctrl-C.
This will write data into two separate files:
./output/flow/<CAPTURE_DATE_TIME>.jsoncontaining json array of received data such as:
{
"AgentIP": "10.0.1.76",
"Bytes": 561,
"DnsErrno": 0,
"Dscp": 20,
"DstAddr": "f904:ece9:ba63:6ac7:8018:1e5:7130:0",
"DstMac": "0A:58:0A:80:00:37",
"DstPort": 9999,
"Duplicate": false,
"Etype": 2048,
"Flags": 16,
"FlowDirection": 0,
"IfDirection": 0,
"Interface": "ens5",
"K8S_FlowLayer": "infra",
"Packets": 1,
"Proto": 6,
"SrcAddr": "3e06:6c10:6440:2:a80:37:b756:270f",
"SrcMac": "0A:58:0A:80:00:01",
"SrcPort": 46934,
"TimeFlowEndMs": 1709741962111,
"TimeFlowRttNs": 121000,
"TimeFlowStartMs": 1709741962111,
"TimeReceived": 1709741964
}./output/flow/<CAPTURE_DATE_TIME>.dbdatabase that can be inspected usingsqlite3for example:
bash-5.1$ sqlite3 ./output/flow/<CAPTURE_DATE_TIME>.db
SQLite version 3.34.1 2021-01-20 14:10:07
Enter ".help" for usage hints.
sqlite> SELECT DnsLatencyMs, DnsFlagsResponseCode, DnsId, DstAddr, DstPort, Interface, Proto, SrcAddr, SrcPort, Bytes, Packets FROM flow WHERE DnsLatencyMs >10 LIMIT 10;
12|NoError|58747|10.128.0.63|57856||17|172.30.0.10|53|284|1
11|NoError|20486|10.128.0.52|56575||17|169.254.169.254|53|225|1
11|NoError|59544|10.128.0.103|51089||17|172.30.0.10|53|307|1
13|NoError|32519|10.128.0.52|55241||17|169.254.169.254|53|254|1
12|NoError|32519|10.0.0.3|55241||17|169.254.169.254|53|254|1
15|NoError|57673|10.128.0.19|59051||17|172.30.0.10|53|313|1
13|NoError|35652|10.0.0.3|46532||17|169.254.169.254|53|183|1
32|NoError|37326|10.0.0.3|52718||17|169.254.169.254|53|169|1
14|NoError|14530|10.0.0.3|58203||17|169.254.169.254|53|246|1
15|NoError|40548|10.0.0.3|45933||17|169.254.169.254|53|174|1For instance, to capture all TCP packets on the cluster that go through port 80:
-
As a
kubectlplugin:kubectl netobserv packets --protocol=TCP --port=80
-
Or from the repository
Makefile:Run the following command to start capturing packets, replacing
USER,VERSIONandCOMMAND_ARGSaccordingly:USER=netobserv VERSION=dev COMMAND_ARGS="--protocol=TCP --port=80" make packets
Similarly to flow capture, it will display a table view with latest flows. However, it will collect packets and write data under output/pcap directory. To stop capturing press Ctrl-C.
This will write pcapng into a single file located in ./output/pcap/<CAPTURE_DATE_TIME>.pcapng that can be opened with Wireshark for example:
We use the pcapng format to add contextual metadata, such as the k8s pods and service names.
For instance, to capture many available metrics, including Packet drops, DNS stats and latenties:
-
As a
kubectlplugin:kubectl netobserv metrics --enable_pkt_drop --enable_dns --enable_rtt
-
Or from the repository
Makefile:Run the following command to start capturing metrics, replacing
USER,VERSIONandCOMMAND_ARGSaccordingly:USER=netobserv VERSION=dev COMMAND_ARGS='--enable_pkt_drop --enable_dns --enable_rtt' make metrics
It will generate a monitoring dashboard called "NetObserv / On Demand" in your Openshift cluster. The url to access it is automatically generated from the CLI. Simply click on the link to open the page.
The cleanup function will automatically remove the eBPF programs when the CLI exits. However you may need to run it manually if running in background or an error occurs.
-
As a
kubectlplugin:kubectl netobserv cleanup
-
Or from the repository
Makefile:USER=netobserv VERSION=dev make cleanup
To build the project locally:
sudo dnf install -y shellcheckmake buildThis will also copy resources and commands to the build directory.
To build your own images of CLI, run the following command replacing USER and VERSION accordingly:
USER=netobserv VERSION=dev make imagesYou can add this plugin to your favorite oc or kubectl commands using the following steps:
K8S_CLI_BIN=oc make install-commandsOR
K8S_CLI_BIN=kubectl make install-commandsThis will add netobserv commands to your CLI.
You can verify the commands are available using:
oc plugin listOR
kubectl plugin listIt will display as result:
The following compatible plugins are available:
...
/usr/bin/<oc|kubectl>-netobservMore info on official OpenShift documentation.



