You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: content/posts/2025-10-28-whats-new-1-10/index.md
+39-48Lines changed: 39 additions & 48 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -16,49 +16,40 @@ The starting point is that you have Red Hat OpenShift web console running and th
16
16
17
17
## FlowCollector Setup UI
18
18
19
-
After [installing Network Observability Operator](https://docs.redhat.com/en/documentation/openshift_container_platform/4.20/html/network_observability/installing-network-observability-operators), you can create a FlowCollector custom resource or instance. This allows you to configure the many parameters of network observability. In this release, there is a new 4-step wizard described below that simplifies the creation of this resource.
19
+
After [installing the Network Observability Operator](https://docs.redhat.com/en/documentation/openshift_container_platform/4.20/html/network_observability/installing-network-observability-operators), you should create a FlowCollector custom resource or instance. This allows you to configure the many parameters of network observability. In this release, there is a new 4-step wizard that simplifies the creation of this resource (Figure 1).
This gives an overview of what FlowCollector is and some basic configuration. The field, **Deploy policies**, will be covered in the section "Improve Security with Network Policies". If you prefer the traditional Form view or the YAML view, since many parameters are not shown in the wizard, click the **FlowCollector form** link in the second paragraph.
24
+
Step 1 gives an overview of what FlowCollector is and some basic configuration. The field, **Deploy policies**, will be covered in the section "Improve Security with Network Policies". If you prefer the traditional Form view or YAML view, since many parameters are not shown in the wizard, click the **FlowCollector form** link in the second paragraph.
Step 2 lets you choose the **Deployment model**, where you can enable Kafka, which is typically necessary for large clusters. This is also where you can enable various eBPF features, many of which help with troubleshooting. And finally, you can choose to include zone information.
27
27
28
-
### Step 2: Processing
28
+
Step 3 configures Loki to store flow logs. Although optional, [without Loki](https://docs.redhat.com/en/documentation/openshift_container_platform/4.20/html/network_observability/installing-network-observability-operators#network-observability-without-loki_network_observability), there will not be a traffic flows table as only metrics will be stored. The default Loki mode is **LokiStack** instead of **Monolithic**.
29
29
30
-
The **Deployment model** is where you can enable Kafka if desired. This is typically necessary for large clusters. You can also enable various eBPF features, many of which help with troubleshooting.
To store flow logs, you need Loki. [Without Loki](https://docs.redhat.com/en/documentation/openshift_container_platform/4.20/html/network_observability/installing-network-observability-operators#network-observability-without-loki_network_observability), there will not be a traffic flows table as only metrics will be stored. The default Loki mode is **LokiStack** instead of **Monolithic**.
Like the FlowCollector Setup, there is a new 4-step wizard for FlowMetric Setup. The FlowMetric CRD lets you define your own custom metrics. The four steps are **Overview**, **Metric** to define the metric name and type, **Data** to specify the direction and filters, and a **Review** panel before applying the change. Figure 6 shows what the first step looks like. The other steps are not shown.
41
+
Like the FlowCollector Setup, there is a new 4-step wizard for FlowMetric Setup (Figure 3). The FlowMetric CRD lets you define your own custom metrics.
42
+
43
+
<br>
44
+
Figure 3: FlowMetric Wizard
45
+
46
+
Step 1 provides an overview of custom metrics. You start off by giving the metric a resource name and a namespace.
47
+
48
+
Step 2 asks for information about the metric, such as the metric name, type (Counter, Histogram, or Gauge), the [name of the field](https://docs.redhat.com/en/documentation/openshift_container_platform/4.20/html/network_observability/json-flows-format-reference) used by this metric called **Value field**, and an optional list of Prometheus labels.
49
+
50
+
Step 3 asks for the direction of the flow and a list of filters to determine what flows you're interested in.
Step 4 displays the manifest (YAML) that will be applied, with the option to edit this before saving.
62
53
63
54
## Improve Security with Network Policies
64
55
@@ -91,10 +82,10 @@ spec:
91
82
- DNSTracking
92
83
```
93
84
94
-
Refresh the browser page and go to **Observe > Alerting**. Click the **Alerting rules** tab. In the dropdown for **Name**, change it to **Label**. Enter `app=netobserv`. You should see the three **DNSErrors_** alerts, in addition to the four **NetObserv** alerts (Figure 7). If not, wait a few seconds. If it still doesn't show up, make sure the changes were accepted in FlowCollector.
85
+
Refresh the browser page and go to **Observe > Alerting**. Click the **Alerting rules** tab. In the dropdown for **Name**, change it to **Label**. Enter `app=netobserv`. You should see the three **DNSErrors_** alerts, in addition to the four **NetObserv** alerts (Figure 4). If not, wait a few seconds. If it still doesn't show up, make sure the changes were accepted in FlowCollector.
95
86
96
87
<br>
97
-
Figure 7: Alerting Rules
88
+
Figure 4: Alerting Rules
98
89
99
90
Here is the FlowCollector configuration if you want to see all the predefined alerts. You must also enable **privileged** mode for PacketDrop.
100
91
@@ -117,25 +108,25 @@ Underneath the covers, it creates a PrometheusRule object. To see what that loo
117
108
118
109
The second Technology Preview is a network health dashboard. The same environmental variable, EXPERIMENTAL_ALERTS_HEALTH, also used for Custom Alerts (see listing above), enables this feature.
119
110
120
-
Refresh the browser, and now there is a new menu panel at **Observe > Network Health** (Figure 8).
111
+
Refresh the browser, and now there is a new menu panel at **Observe > Network Health** (Figure 5).
121
112
122
113
<br>
123
-
Figure 8: Network Health Dashboard
114
+
Figure 5: Network Health Dashboard
124
115
125
-
At the top of the Network Health dashboard, it gives an overall summary of the network health. Below that, there are three tabs named **Global**, **Nodes**, and **Namespaces**. The **Global** tab shows the global rule violations (Figure 9). In this screenshot, it reports "Too many DNS errors".
116
+
At the top of the Network Health dashboard, it gives an overall summary of the network health. Below that, there are three tabs named **Global**, **Nodes**, and **Namespaces**. The **Global** tab shows the global rule violations (Figure 6). In this screenshot, it reports "Too many DNS errors".
126
117
127
118
<br>
128
-
Figure 9: Network Health - Global
119
+
Figure 6: Network Health - Global
129
120
130
-
The **Nodes** tab shows rule violations at the node level(Figure 10). There are none in this screenshot.
121
+
The **Nodes** tab shows rule violations at the node level(Figure 7). There are none in this screenshot.
131
122
132
123
<br>
133
-
Figure 10: Network Health - Nodes
124
+
Figure 7: Network Health - Nodes
134
125
135
126
The **Namespaces** tab shows rule violations at the namespace level.
136
127
137
128
<br>
138
-
Figure 11: Network Health - Namespaces
129
+
Figure 8: Network Health - Namespaces
139
130
140
131
## Network Observability CLI 1.10
141
132
@@ -148,24 +139,24 @@ I'll go over the three main modes and describe the changes in this release. If
148
139
149
140
### Flows
150
141
151
-
To see the traffic flows table, enter `oc netobserv flows`, and add any other options to the command. By default, it runs in dark mode (Figure 12).
142
+
To see the traffic flows table, enter `oc netobserv flows`, and add any other options to the command. By default, it runs in dark mode (Figure 9).
The blue square at the top has a number of controls. The triangle is a new play/pause button that's accessible with the mouse. This is a nice addition to be able to pause the data. Note that while it's paused, data is still being collected.
157
148
158
149
Below the play/pause button are the "-" and "+" buttons. Each row corresponds to decreasing or increasing the value on that same row. Therefore, the first set of buttons decreases or increases how many rows to display. The next row, **Display**, cycles through the eBPF features. The last row, **Enrichment**, shows different columns.
159
150
160
-
The **Manage columns** button is new (Figure 13). It lets you select a set of columns to display. Select or deselect a column using the Enter key (not the mouse).
151
+
The **Manage columns** button is new (Figure 10). It lets you select a set of columns to display. Select or deselect a column using the Enter key (not the mouse).
The filter field at the bottom of the screen was improved. As you type into this field, it provides auto-suggestions in a dropdown choicelist (Figure 14). You can also enter multiple filters.
156
+
The filter field at the bottom of the screen was improved. As you type into this field, it provides auto-suggestions in a dropdown choicelist (Figure 11). You can also enter multiple filters.
Use the tab key to toggle between the flows table and the filter field. While in the table, you can move around using the `h,j,k,l` keys, for those of you who are familiar with vi!
171
162
@@ -178,21 +169,21 @@ To view the metrics, enter `oc netobserv metrics --enable_all` plus any other op
178
169
In the previous release, you could only see graphs with the OpenShift web console. Now there are text-based graphs!
In the blue box, you can increase or decrease the number of points in the graph by increments of 5, You can also cycle through the different sets of graphs in the **Display** row. If you want the OpenShift web console to display the graphs like before, add the `--background` option.
184
175
185
-
There is a **Manage panels** button that lets you choose the graphs you want to display (Figure 16). Select or deselect a panel using the Enter key (not the mouse).
176
+
There is a **Manage panels** button that lets you choose the graphs you want to display (Figure 13). Select or deselect a panel using the Enter key (not the mouse).
To view packets, enter `oc netobserv packets <filter>`. A filter is required such as `oc netobserv packets --port=443`. If you want to inspect a packet, you can do that directly now without having to resort to an external tool like Wireshark (Figure 17). Press tab to go to the table. Move to the particular row and press Enter.
183
+
To view packets, enter `oc netobserv packets <filter>`. A filter is required such as `oc netobserv packets --port=443`. If you want to inspect a packet, you can do that directly now without having to resort to an external tool like Wireshark (Figure 14). Press tab to go to the table. Move to the particular row and press Enter.
0 commit comments