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: observability/network_observability/network-observability-operator-release-notes.adoc
+3-8Lines changed: 3 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -454,8 +454,7 @@ You can configure the `FlowCollector` resource to collect information about the
454
454
==== Notable enhancements
455
455
The 1.5 release of the Network Observability Operator adds improvements and new capabilities to the {product-title} web console plugin and the Operator configuration.
456
456
457
-
[discrete]
458
-
[id="performance-enhancements-1.5"]
457
+
[id="performance-enhancements-1.5_{context}"]
459
458
===== Performance enhancements
460
459
* The `spec.agent.ebpf.kafkaBatchSize` default is changed from `10MB` to `1MB` to enhance eBPF performance when using Kafka.
461
460
+
@@ -464,8 +463,7 @@ The 1.5 release of the Network Observability Operator adds improvements and new
464
463
When upgrading from an existing installation, this new value is not set automatically in the configuration. If you monitor a performance regression with the eBPF Agent memory consumption after upgrading, you might consider reducing the `kafkaBatchSize` to the new value.
465
464
=====
466
465
467
-
[discrete]
468
-
[id="web-console-enhancements-1.5"]
466
+
[id="web-console-enhancements-1.5_{context}"]
469
467
===== Web console enhancements:
470
468
471
469
* There are new panels added to the *Overview* view for DNS and RTT: Min, Max, P90, P99.
@@ -477,8 +475,7 @@ When upgrading from an existing installation, this new value is not set automati
477
475
* There is enhanced visibility for the contents of the *Manage panels* and *Manage columns* pop-up windows.
478
476
* The Differentiated Services Code Point (DSCP) field for egress QoS is available for filtering QoS DSCP in the web console *Network Traffic* page.
479
477
480
-
[discrete]
481
-
[id="configuration-enhancements-1.5"]
478
+
[id="configuration-enhancements-1.5_{context}"]
482
479
===== Configuration enhancements:
483
480
484
481
* The `LokiStack` mode in the `spec.loki.mode` specification simplifies installation by automatically setting URLs, TLS, cluster roles and a cluster role binding, as well as the `authToken` value. The `Manual` mode allows more control over configuration of these settings.
@@ -556,7 +553,6 @@ You must switch your channel from `v1.0.x` to `stable` to receive the latest Ope
556
553
==== Notable enhancements
557
554
The 1.4 release of the Network Observability Operator adds improvements and new capabilities to the {product-title} web console plugin and the Operator configuration.
558
555
559
-
[discrete]
560
556
[id="web-console-enhancements-1.4_{context}"]
561
557
===== Web console enhancements:
562
558
@@ -569,7 +565,6 @@ The 1.4 release of the Network Observability Operator adds improvements and new
569
565
570
566
For more information, see xref:../../observability/network_observability/network-observability-overview.adoc#network-observability-dashboards_network-observability-overview[Network observability metrics dashboards] and xref:../../observability/network_observability/observing-network-traffic.adoc#network-observability-quickfilter_nw-observe-network-traffic[Quick filters].
Copy file name to clipboardExpand all lines: observability/network_observability/network-observability-secondary-networks.adoc
+2-3Lines changed: 2 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -8,9 +8,8 @@ toc::[]
8
8
You can configure the Network Observability Operator to collect and enrich network flow data from secondary networks, such as SR-IOV and OVN-Kubernetes.
9
9
10
10
// Note to tech review:
11
-
// Is the existing SR-IOV example we have, "Configuring monitoring for SR-IOV interface traffic", an example of secondary network? If so, it is not through a VM, right?
11
+
// Is the existing SR-IOV example we have, "Configuring monitoring for SR-IOV interface traffic", an example of secondary network? If so, it is not through a VM, right?
*xref:../../networking/hardware_networks/configuring-sriov-device.adoc#cnf-creating-an-additional-sriov-network-with-vrf-plug-in_configuring-sriov-device[Creating an additional SR-IOV network attachment with the CNI VRF plugin].
21
+
*xref:../../networking/hardware_networks/configuring-sriov-device.adoc#cnf-creating-an-additional-sriov-network-with-vrf-plug-in_configuring-sriov-device[Configuring an SR-IOV network device]
0 commit comments