Skip to content

fix missing code section #10

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
jpinsonneau merged 1 commit into from
Feb 12, 2025
Merged

fix missing code section #10

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 3 additions & 1 deletion content/posts/2025-02-11-cli_whats_new_1.8.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -74,6 +74,8 @@ Filtering is crucial to gather precise network data without involving excessive
It's now possible to define agents `nodeSelector` to capture on a subset of nodes. You can rely on existing labels or create a dedicated one for this usage. For example, you can run the agents on the node with the `kubernetes.io/hostname:my-node` label with the following command:
```sh
oc netobserv flows --node-selector=kubernetes.io/hostname:my-node
```

### eBPF Filters
Agents recently introduced [the ability to filter](https://github.com/netobserv/netobserv-ebpf-agent/blob/main/docs/flow_filtering.md) on IPs, Ports, Protocol, Action, TCPFlags, and more simultaneously. You can now apply these filters in the CLI as shown below:

Expand Down Expand Up @@ -127,7 +129,7 @@ oc netobserv metrics --enable_all
```
to capture packet drops, DNS and RTT metrics or
```sh
oc netobserv metrics --enable_pktdrop
oc netobserv metrics --enable_pkt_drop
```
to focus only on drops.

Expand Down