|
| 1 | +// Module included in the following assemblies: |
| 2 | +// * network_observability/release_notes_archive/network-observability-operator-release-notes-archive.adoc |
| 3 | + |
| 4 | +:_mod-docs-content-type: REFERENCE |
| 5 | +[id="network-observability-operator-release-notes-1-6-0-new-features-and-enhancements_{context}"] |
| 6 | += Network Observability Operator 1.6.0 new features and enhancements |
| 7 | + |
| 8 | +[role="_abstract"] |
| 9 | +You can review the following new features and enhancements for the Network Observability Operator 1.6.0. |
| 10 | + |
| 11 | +[id="network-observability-lokiless-enhancements-1.6_{context}"] |
| 12 | +== Enhanced use of Network Observability Operator without Loki |
| 13 | +You can now use Prometheus metrics and rely less on Loki for storage when using the Network Observability Operator. |
| 14 | + |
| 15 | +// For more information, see xref:../../observability/network_observability/installing-operators.adoc#network-observability-without-loki_network_observability[Network observability without Loki]. |
| 16 | + |
| 17 | +[id="network-observability-custom-metrics-1.6_{context}"] |
| 18 | +== Custom metrics API |
| 19 | +You can create custom metrics out of flowlogs data by using the `FlowMetrics` API. Flowlogs data can be used with Prometheus labels to customize cluster information on your dashboards. You can add custom labels for any subnet that you want to identify in your flows and metrics. This enhancement can also be used to more easily identify external traffic by using the new labels `SrcSubnetLabel` and `DstSubnetLabel`, which exists both in flow logs and in metrics. Those fields are empty when there is external traffic, which gives a way to identify it. |
| 20 | + |
| 21 | +//For more information, see xref:../../observability/network_observability/metrics-alerts-dashboards.adoc#network-observability-custom-metrics_metrics-dashboards-alerts[Custom metrics] and xref:../../observability/network_observability/flowmetric-api.adoc#flowmetric-flows-netobserv-io-v1alpha1[FlowMetric API reference]. |
| 22 | + |
| 23 | +[id="network-observability-eBPF-performance-enhancements-1.6_{context}"] |
| 24 | +== eBPF performance enhancements |
| 25 | +Experience improved performances of the eBPF agent, in terms of CPU and memory, with the following updates: |
| 26 | + |
| 27 | +* The eBPF agent now uses TCX webhooks instead of TC. |
| 28 | +* The *NetObserv / Health* dashboard has a new section that shows eBPF metrics. |
| 29 | +** Based on the new eBPF metrics, an alert notifies you when the eBPF agent is dropping flows. |
| 30 | +* Loki storage demand decreases significantly now that duplicated flows are removed. Instead of having multiple, individual duplicated flows per network interface, there is one de-duplicated flow with a list of related network interfaces. |
| 31 | + |
| 32 | +[IMPORTANT] |
| 33 | +===== |
| 34 | +With the duplicated flows update, the *Interface* and *Interface Direction* fields in the *Network Traffic* table are renamed to *Interfaces* and *Interface Directions*, so any bookmarked *Quick filter* queries using these fields need to be updated to `interfaces` and `ifdirections`. |
| 35 | +===== |
| 36 | +//// |
| 37 | +For more information, see xref:../../observability/network_observability/network-observability-operator-monitoring.adoc#network-observability-netobserv-dashboard-ebpf-agent-alerts_network_observability[Using the eBPF agent alert] |
| 38 | +and 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[Filtering the network traffic]. |
| 39 | +//// |
| 40 | + |
| 41 | +[id="network-observability-ebpf-collection-filtering-1.6_{context}"] |
| 42 | +== eBPF collection rule-based filtering |
| 43 | +You can use rule-based filtering to reduce the volume of created flows. When this option is enabled, the *Netobserv / Health* dashboard for eBPF agent statistics has the *Filtered flows rate* view. |
| 44 | + |
| 45 | +//For more information, see xref:../../observability/network_observability/observing-network-traffic.adoc#network-observability-ebpf-flow-rule-filter_nw-observe-network-traffic[eBPF flow rule filter]. |
0 commit comments