OSDOCS-17329 [NETOBSERV] xrefs in Release Note modules

Author: gwynnemonahan

…bility-release-notes-1-4-0-advisory.adoc …erator-release-notes-1-4-0-advisory.adocmodules/network-observability-release-notes-1-4-0-advisory.adoc renamed to modules/network-observability-operator-release-notes-1-4-0-advisory.adoc modules/network-observability-release-notes-1-4-0-advisory.adoc renamed to modules/network-observability-operator-release-notes-1-4-0-advisory.adoc

@@ -21,63 +21,76 @@ The 1.4 release of the Network Observability Operator adds improvements and new
 ** The *NetObserv / Health* dashboard shows flows overhead as well as top flow rates per nodes, namespaces, and workloads.
 ** Infrastructure and Application metrics are shown in a split-view for namespaces and workloads.
 
-////
-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].
-////
+
+For more information, see:
+
+* xref:../../../observability/network_observability/network-observability-overview.adoc#network-observability-dashboards_network-observability-overview[Network observability metrics dashboards]
+* xref:../../../observability/network_observability/observing-network-traffic.adoc#network-observability-quickfilter_nw-observe-network-traffic[Quick filters]
+
 
 [id="configuration-enhancements-1.4_{context}"]
 == Configuration enhancements:
 * You now have the option to specify different namespaces for any configured ConfigMap or Secret reference, such as in certificates configuration.
 * The `spec.processor.clusterName` parameter is added so that the name of the cluster appears in the flows data. This is useful in a multi-cluster context. When using {product-title}, leave empty to make it automatically determined.
 
-////
-For more information, see the following links:
+
+For more information, see:
+
 * xref:../../../observability/network_observability/configuring-operator.adoc#network-observability-flowcollector-view_network_observability[Flow Collector sample resource]
-* xref:../../../observability/network_observability/flowcollector-api.adoc#network-observability-flowcollector-api-specifications_network_observability[Flow Collector API Reference].
-////
+* xref:../../../observability/network_observability/flowcollector-api.adoc#network-observability-flowcollector-api-specifications_network_observability[Flow Collector API Reference]
+
 
 [id="network-observability-without-loki-1.4_{context}"]
 == Network observability without Loki
 The Network Observability Operator is now functional and usable without Loki. If Loki is not installed, it can only export flows to KAFKA or IPFIX format and provide metrics in the network observability metrics dashboards.
 
-////
-For more information, see the following link:
-* xref:../../../observability/network_observability/installing-operators.adoc#network-observability-without-loki_network_observability[Network observability without Loki].
-////
+
+For more information, see:
+
+* xref:../../../observability/network_observability/installing-operators.adoc#network-observability-without-loki_network_observability[Network observability without Loki]
+
 
 [id="network-observability-dns-tracking-1.4_{context}"]
 == DNS tracking
 In 1.4, the Network Observability Operator makes use of eBPF tracepoint hooks to enable DNS tracking. You can monitor your network, conduct security analysis, and troubleshoot DNS issues in the *Network Traffic* and *Overview* pages in the web console.
 
-////
-For more information, see the following links:
+
+For more information, see:
+
 * xref:../../../observability/network_observability/observing-network-traffic.adoc#network-observability-dns-overview_nw-observe-network-traffic[Configuring DNS tracking]
 * xref:../../../observability/network_observability/observing-network-traffic.adoc#network-observability-dns-tracking_nw-observe-network-traffic[Working with DNS tracking]
-////
+
 
 [id="SR-IOV-configuration-1.4_{context}"]
 == SR-IOV support
 You can now collect traffic from a cluster with Single Root I/O Virtualization (SR-IOV) device.
 
-////
-For more information, see xref:../../../observability/network_observability/network-observability-secondary-networks.adoc#network-observability-SR-IOV-config_network-observability-secondary-networks[Configuring the monitoring of SR-IOV interface traffic].
-////
+
+For more information, see:
+
+* xref:../../../observability/network_observability/network-observability-secondary-networks.adoc#network-observability-SR-IOV-config_network-observability-secondary-networks[Configuring the monitoring of SR-IOV interface traffic]
+
 
 [id="IPFIX-support-1.4_{context}"]
 == IPFIX exporter support
 You can now export eBPF-enriched network flows to the IPFIX collector.
 
-////
-For more information, see xref:../../../observability/network_observability/configuring-operator.adoc#network-observability-enriched-flows_network_observability[Export enriched network flow data].
-////
+
+For more information, see:
+
+* xref:../../../observability/network_observability/configuring-operator.adoc#network-observability-enriched-flows_network_observability[Export enriched network flow data]
+
 
 [id="network-observability-packet-drop-1.4_{context}"]
 == Packet drops
 In the 1.4 release of the Network Observability Operator, eBPF tracepoint hooks are used to enable packet drop tracking. You can now detect and analyze the cause for packet drops and make decisions to optimize network performance. In {product-title} 4.14 and later, both host drops and OVS drops are detected. In {product-title} 4.13, only host drops are detected.
 
-////
-For more information, see xref:../../../observability/network_observability/observing-network-traffic.adoc#network-observability-pktdrop-overview_nw-observe-network-traffic[Configuring packet drop tracking] and xref:../../../observability/network_observability/observing-network-traffic.adoc#network-observability-packet-drops_nw-observe-network-traffic[Working with packet drops].
-////
+
+For more information, see:
+
+* xref:../../../observability/network_observability/observing-network-traffic.adoc#network-observability-pktdrop-overview_nw-observe-network-traffic[Configuring packet drop tracking]
+* xref:../../../observability/network_observability/observing-network-traffic.adoc#network-observability-packet-drops_nw-observe-network-traffic[Working with packet drops]
+
 
 [id="s390x-architecture-support_{context}"]
 == s390x architecture support

…ty-release-notes-1-4-0-fixed-issues.adoc …or-release-notes-1-4-0-fixed-issues.adocmodules/network-observability-release-notes-1-4-0-fixed-issues.adoc renamed to modules/network-observability-operator-release-notes-1-4-0-fixed-issues.adoc modules/network-observability-release-notes-1-4-0-fixed-issues.adoc renamed to modules/network-observability-operator-release-notes-1-4-0-fixed-issues.adoc

@@ -12,41 +12,52 @@ You can view the following new features and enhancements for the Network Observa
 == DNS tracking enhancements
 In 1.5, the TCP protocol is now supported in addition to UDP. New dashboards are also added to the *Overview* view of the Network Traffic page.
 
-////
-For more information, see xref:../../observability/network_observability/observing-network-traffic.adoc#network-observability-dns-overview_nw-observe-network-traffic[Configuring DNS tracking] and xref:../../observability/network_observability/observing-network-traffic.adoc#network-observability-dns-tracking_nw-observe-network-traffic[Working with DNS tracking].
-////
+For more information, see:
+
+* xref:../../../observability/network_observability/observing-network-traffic.adoc#network-observability-dns-overview_nw-observe-network-traffic[Configuring DNS tracking]
+* xref:../../../observability/network_observability/observing-network-traffic.adoc#network-observability-dns-tracking_nw-observe-network-traffic[Working with DNS tracking]
+
 
 [id="network-observability-RTT-1.5_{context}"]
 == Round-trip time (RTT)
 You can use TCP handshake Round-Trip Time (RTT) captured from the `fentry/tcp_rcv_established` Extended Berkeley Packet Filter (eBPF) hookpoint to read smoothed round-trip time (SRTT) and analyze network flows. In the *Overview*, *Network Traffic*, and *Topology* pages in web console, you can monitor network traffic and troubleshoot with RTT metrics, filtering, and edge labeling.
 
-////
-For more information, see xref:../../observability/network_observability/observing-network-traffic.adoc#network-observability-RTT-overview_nw-observe-network-traffic[RTT Overview] and xref:../../observability/network_observability/observing-network-traffic.adoc#network-observability-RTT_nw-observe-network-traffic[Working with RTT].
-////
+
+For more information, see:
+
+* xref:../../../observability/network_observability/observing-network-traffic.adoc#network-observability-RTT-overview_nw-observe-network-traffic[RTT Overview]
+* xref:../../../observability/network_observability/observing-network-traffic.adoc#network-observability-RTT_nw-observe-network-traffic[Working with RTT]
+
 
 [id="network-observability-metrics-dashboard-enhancements_{context}"]
 == Metrics, dashboards, and alerts enhancements
 The network observability metrics dashboards in *Observe* → *Dashboards* → *NetObserv* have new metrics types you can use to create Prometheus alerts. You can now define available metrics in the `includeList` specification. In previous releases, these metrics were defined in the `ignoreTags` specification.
 
-////
-For a complete list of these metrics, see xref:../../observability/network_observability/metrics-alerts-dashboards.adoc#network-observability-metrics_metrics-dashboards-alerts[Network observability metrics].
-////
+
+For a complete list of these metrics, see:
+
+* xref:../../../observability/network_observability/metrics-alerts-dashboards.adoc#network-observability-metrics_metrics-dashboards-alerts[Network observability metrics]
+
 
 [id="network-observability-improved-lokistack-integration_{context}"]
 == Improvements for network observability without Loki
 You can create Prometheus alerts for the *Netobserv* dashboard using DNS, Packet drop, and RTT metrics, even if you don't use Loki. In the previous version of network observability, 1.4, these metrics were only available for querying and analysis in the *Network Traffic*, *Overview*, and *Topology* views, which are not available without Loki.
 
-////
-For more information, see xref:../../observability/network_observability/metrics-alerts-dashboards.adoc#network-observability-metrics_metrics-dashboards-alerts[Network observability metrics]
-////
+
+For more information, see:
+
+* xref:../../../observability/network_observability/metrics-alerts-dashboards.adoc#network-observability-metrics_metrics-dashboards-alerts[Network observability metrics]
+
 
 [id="network-observability-zones_{context}"]
 == Availability zones
 You can configure the `FlowCollector` resource to collect information about the cluster availability zones. This configuration enriches the network flow data with the link:https://kubernetes.io/docs/reference/labels-annotations-taints/#topologykubernetesiozone[`topology.kubernetes.io/zone`] label value applied to the nodes.
 
-////
-For more information, see xref:../../observability/network_observability/observing-network-traffic.adoc#network-observability-zones_nw-observe-network-traffic[Working with availability zones]
-////
+
+For more information, see:
+
+* xref:../../../observability/network_observability/observing-network-traffic.adoc#network-observability-zones_nw-observe-network-traffic[Working with availability zones]
+
 
 [id="network-observability-enhanced-configuration-and-ui-1.5_{context}"]
 == Notable enhancements

…ty-release-notes-1-4-0-known-issues.adoc …or-release-notes-1-4-0-known-issues.adocmodules/network-observability-release-notes-1-4-0-known-issues.adoc renamed to modules/network-observability-operator-release-notes-1-4-0-known-issues.adoc modules/network-observability-release-notes-1-4-0-known-issues.adoc renamed to modules/network-observability-operator-release-notes-1-4-0-known-issues.adoc

@@ -12,13 +12,18 @@ You can review the following new features and enhancements for the Network Obser
 == Enhanced use of Network Observability Operator without Loki
 You can now use Prometheus metrics and rely less on Loki for storage when using the Network Observability Operator.
 
-// For more information, see xref:../../observability/network_observability/installing-operators.adoc#network-observability-without-loki_network_observability[Network observability without Loki].
+For more information, see:
+
+* xref:../../../observability/network_observability/installing-operators.adoc#network-observability-without-loki_network_observability[Network observability without Loki]
 
 [id="network-observability-custom-metrics-1.6_{context}"]
 == Custom metrics API
 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.
 
-//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].
+For more information, see:
+
+* xref:../../../observability/network_observability/metrics-alerts-dashboards.adoc#network-observability-custom-metrics_metrics-dashboards-alerts[Custom metrics]
+* xref:../../../observability/network_observability/flowmetric-api.adoc#flowmetric-flows-netobserv-io-v1alpha1[FlowMetric API reference]
 
 [id="network-observability-eBPF-performance-enhancements-1.6_{context}"]
 == eBPF performance enhancements
@@ -33,13 +38,18 @@ Experience improved performances of the eBPF agent, in terms of CPU and memory,
 =====
 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`.
 =====
-////
-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]
-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].
-////
+
+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]
+* xref:../../../observability/network_observability/network-observability-overview.adoc#network-observability-dashboards_network-observability-overview[Network observability metrics dashboards]
+* xref:../../../observability/network_observability/observing-network-traffic.adoc#network-observability-quickfilter_nw-observe-network-traffic[Filtering the network traffic]
+
 
 [id="network-observability-ebpf-collection-filtering-1.6_{context}"]
 == eBPF collection rule-based filtering
 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.
 
-//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].
+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]