From eb9cc4033e9cbbd9c3d2432ca410aba608e4acd0 Mon Sep 17 00:00:00 2001 From: Sara Thomas Date: Thu, 21 Mar 2024 10:56:57 -0400 Subject: [PATCH] OBSDOCS-695:Update Network Observability doc links and topic map position --- _topic_maps/_topic_map.yml | 57 ++++++++-------- .../installing-operators.adoc | 67 ------------------- networking/networking-dashboards.adoc | 2 +- networking/networking-operators-overview.adoc | 2 +- observability/index.adoc | 3 +- .../network_observability}/_attributes | 0 .../configuring-operator.adoc | 6 +- .../flowcollector-api.adoc | 0 .../network_observability}/images | 0 .../installing-operators.adoc | 67 +++++++++++++++++++ .../json-flows-format-reference.adoc | 0 .../metrics-alerts-dashboards.adoc | 2 +- .../network_observability}/modules | 0 .../network-observability-network-policy.adoc | 2 +- ...ork-observability-operator-monitoring.adoc | 2 +- ...-observability-operator-release-notes.adoc | 42 ++++++------ .../network-observability-overview.adoc | 0 .../observing-network-traffic.adoc | 12 ++-- .../network_observability}/snippets | 0 ...troubleshooting-network-observability.adoc | 2 +- ...anding-network-observability-operator.adoc | 0 welcome/index.adoc | 3 +- 22 files changed, 133 insertions(+), 136 deletions(-) delete mode 100644 network_observability/installing-operators.adoc rename {network_observability => observability/network_observability}/_attributes (100%) rename {network_observability => observability/network_observability}/configuring-operator.adoc (67%) rename {network_observability => observability/network_observability}/flowcollector-api.adoc (100%) rename {network_observability => observability/network_observability}/images (100%) create mode 100644 observability/network_observability/installing-operators.adoc rename {network_observability => observability/network_observability}/json-flows-format-reference.adoc (100%) rename {network_observability => observability/network_observability}/metrics-alerts-dashboards.adoc (80%) rename {network_observability => observability/network_observability}/modules (100%) rename {network_observability => observability/network_observability}/network-observability-network-policy.adoc (78%) rename {network_observability => observability/network_observability}/network-observability-operator-monitoring.adoc (79%) rename {network_observability => observability/network_observability}/network-observability-operator-release-notes.adoc (86%) rename {network_observability => observability/network_observability}/network-observability-overview.adoc (100%) rename {network_observability => observability/network_observability}/observing-network-traffic.adoc (68%) rename {network_observability => observability/network_observability}/snippets (100%) rename {network_observability => observability/network_observability}/troubleshooting-network-observability.adoc (88%) rename {network_observability => observability/network_observability}/understanding-network-observability-operator.adoc (100%) diff --git a/_topic_maps/_topic_map.yml b/_topic_maps/_topic_map.yml index 5831874ae4ed..4038beae2fb4 100644 --- a/_topic_maps/_topic_map.yml +++ b/_topic_maps/_topic_map.yml @@ -2667,6 +2667,34 @@ Topics: File: otel-updating - Name: Removal File: otel-removing +- Name: Network Observability + Dir: network_observability + Distros: openshift-enterprise,openshift-origin + Topics: + - Name: Network Observability release notes + File: network-observability-operator-release-notes + - Name: Network Observability overview + File: network-observability-overview + - Name: Installing the Network Observability Operator + File: installing-operators + - Name: Understanding Network Observability Operator + File: understanding-network-observability-operator + - Name: Configuring the Network Observability Operator + File: configuring-operator + - Name: Network Policy + File: network-observability-network-policy + - Name: Observing the network traffic + File: observing-network-traffic + - Name: Using metrics with dashboards and alerts + File: metrics-alerts-dashboards + - Name: Monitoring the Network Observability Operator + File: network-observability-operator-monitoring + - Name: API reference + File: flowcollector-api + - Name: JSON flows format reference + File: json-flows-format-reference + - Name: Troubleshooting Network Observability + File: troubleshooting-network-observability - Name: Power Monitoring Dir: power_monitoring Distros: openshift-enterprise,openshift-origin @@ -2836,35 +2864,6 @@ Topics: - Name: Configuring the Cluster Observability Operator to monitor a service File: configuring-the-cluster-observability-operator-to-monitor-a-service --- -Name: Network Observability -Dir: network_observability -Distros: openshift-enterprise,openshift-origin -Topics: -- Name: Network Observability release notes - File: network-observability-operator-release-notes -- Name: Network Observability overview - File: network-observability-overview -- Name: Installing the Network Observability Operator - File: installing-operators -- Name: Understanding Network Observability Operator - File: understanding-network-observability-operator -- Name: Configuring the Network Observability Operator - File: configuring-operator -- Name: Network Policy - File: network-observability-network-policy -- Name: Observing the network traffic - File: observing-network-traffic -- Name: Using metrics with dashboards and alerts - File: metrics-alerts-dashboards -- Name: Monitoring the Network Observability Operator - File: network-observability-operator-monitoring -- Name: API reference - File: flowcollector-api -- Name: JSON flows format reference - File: json-flows-format-reference -- Name: Troubleshooting Network Observability - File: troubleshooting-network-observability ---- Name: Scalability and performance Dir: scalability_and_performance Distros: openshift-origin,openshift-enterprise,openshift-webscale,openshift-dpu diff --git a/network_observability/installing-operators.adoc b/network_observability/installing-operators.adoc deleted file mode 100644 index 21939fa6fde2..000000000000 --- a/network_observability/installing-operators.adoc +++ /dev/null @@ -1,67 +0,0 @@ -:_mod-docs-content-type: ASSEMBLY -[id="installing-network-observability-operators"] -= Installing the Network Observability Operator -include::_attributes/common-attributes.adoc[] -:context: network_observability - -toc::[] -Installing Loki is a recommended prerequisite for using the Network Observability Operator. You can choose to use xref:../network_observability/installing-operators.adoc#network-observability-without-loki_network_observability[Network Observability without Loki], but there are some considerations for doing this, described in the previously linked section. - -The {loki-op} integrates a gateway that implements multi-tenancy and authentication with Loki for data flow storage. The `LokiStack` resource manages Loki, which is a scalable, highly-available, multi-tenant log aggregation system, and a web proxy with {product-title} authentication. The `LokiStack` proxy uses {product-title} authentication to enforce multi-tenancy and facilitate the saving and indexing of data in Loki log stores. - -[NOTE] -==== -The {loki-op} can also be used for xref:../logging/log_storage/cluster-logging-loki.adoc#cluster-logging-loki[configuring the LokiStack log store]. The Network Observability Operator requires a dedicated LokiStack separate from the {logging}. -==== - -include::modules/network-observability-without-loki.adoc[leveloffset=+1] - -[role="_additional-resources"] -.Additional resources -* xref:../network_observability/configuring-operator.adoc#network-observability-enriched-flows_network_observability[Export enriched network flow data]. - -include::modules/network-observability-loki-install.adoc[leveloffset=+1] -include::modules/network-observability-loki-secret.adoc[leveloffset=+2] -[role="_additional-resources"] -.Additional resources -* xref:../network_observability/flowcollector-api.adoc#network-observability-flowcollector-api-specifications_network_observability[Flow Collector API Reference] -* xref:../network_observability/configuring-operator.adoc#network-observability-flowcollector-view_network_observability[Flow Collector sample resource] -* xref:../logging/log_storage/installing-log-storage.adoc#logging-loki-storage_installing-log-storage[Loki object storage] - -include::modules/network-observability-lokistack-create.adoc[leveloffset=+2] -include::modules/logging-creating-new-group-cluster-admin-user-role.adoc[leveloffset=+2] -include::modules/logging-loki-log-access.adoc[leveloffset=+1,tags=CustomAdmin;NetObservMode;!LokiMode] -include::modules/loki-deployment-sizing.adoc[leveloffset=+2] -include::modules/network-observability-lokistack-ingestion-query.adoc[leveloffset=+2] -include::modules/network-observability-multitenancy.adoc[leveloffset=+2] -include::modules/network-observability-operator-install.adoc[leveloffset=+1] - -[role="_additional-resources"] -[id="additional-resources_configuring-flow-collector-considerations"] -== Important Flow Collector configuration considerations -Once you create the `FlowCollector` instance, you can reconfigure it, but the pods are terminated and recreated again, which can be disruptive. Therefore, you can consider configuring the following options when creating the `FlowCollector` for the first time: - -* xref:../network_observability/configuring-operator.adoc#network-observability-flowcollector-kafka-config_network_observability[Configuring the Flow Collector resource with Kafka] -* xref:../network_observability/configuring-operator.adoc#network-observability-enriched-flows_network_observability[Export enriched network flow data to Kafka or IPFIX] -* xref:../network_observability/configuring-operator.adoc#network-observability-SR-IOV-config_network_observability[Configuring monitoring for SR-IOV interface traffic] -* xref:../network_observability/observing-network-traffic.adoc#network-observability-working-with-conversations_nw-observe-network-traffic[Working with conversation tracking] -* xref:../network_observability/observing-network-traffic.adoc#network-observability-dns-tracking_nw-observe-network-traffic[Working with DNS tracking] -* xref:../network_observability/observing-network-traffic.adoc#network-observability-packet-drops_nw-observe-network-traffic[Working with packet drops] - -[role="_additional-resources"] -.Additional resources -For more general information about Flow Collector specifications and the Network Observability Operator architecture and resource use, see the following resources: - -* xref:../network_observability/flowcollector-api.adoc#network-observability-flowcollector-api-specifications_network_observability[Flow Collector API Reference] -* xref:../network_observability/configuring-operator.adoc#network-observability-flowcollector-view_network_observability[Flow Collector sample resource] -* xref:../network_observability/configuring-operator.adoc#network-observability-resources-table_network_observability[Resource considerations] -* xref:../network_observability/troubleshooting-network-observability.adoc#controller-manager-pod-runs-out-of-memory_network-observability-troubleshooting[Troubleshooting Network Observability controller manager pod runs out of memory] -* xref:../network_observability/understanding-network-observability-operator.adoc#network-observability-architecture_nw-network-observability-operator[Network Observability architecture] - - -include::modules/network-observability-kafka-option.adoc[leveloffset=+1] -[role="_additional-resources"] -.Additional resources -xref:../network_observability/configuring-operator.adoc#network-observability-flowcollector-kafka-config_network_observability[Configuring the FlowCollector resource with Kafka]. - -include::modules/network-observability-operator-uninstall.adoc[leveloffset=+1] diff --git a/networking/networking-dashboards.adoc b/networking/networking-dashboards.adoc index 58fc6c730b84..cbbd52f686d1 100644 --- a/networking/networking-dashboards.adoc +++ b/networking/networking-dashboards.adoc @@ -10,7 +10,7 @@ Networking metrics are viewable in dashboards within the {product-title} web con [id="network-observability-operator-operator-dashboards"] == Network Observability Operator -If you have the Network Observability Operator installed, you can view network traffic metrics dashboards by selecting the *Netobserv* dashboard from the *Dashboards* drop-down list. For more information about metrics available in this *Dashboard*, see xref:../network_observability/metrics-alerts-dashboards.adoc#network-observability-viewing-dashboards_metrics-dashboards-alerts[Network Observability metrics dashboards] +If you have the Network Observability Operator installed, you can view network traffic metrics dashboards by selecting the *Netobserv* dashboard from the *Dashboards* drop-down list. For more information about metrics available in this *Dashboard*, see xref:../observability/network_observability/metrics-alerts-dashboards.adoc#network-observability-viewing-dashboards_metrics-dashboards-alerts[Network Observability metrics dashboards]. [id="general-networking-ovnk-dashboards"] == Networking and OVN-Kubernetes dashboard diff --git a/networking/networking-operators-overview.adoc b/networking/networking-operators-overview.adoc index 9b1fbd3c3925..6db9ed9b81aa 100644 --- a/networking/networking-operators-overview.adoc +++ b/networking/networking-operators-overview.adoc @@ -30,4 +30,4 @@ The Ingress Node Firewall Operator uses an extended Berkley Packet Filter (eBPF) [id="network-observability-operator-overview-operator"] == Network Observability Operator -The Network Observability Operator is an optional Operator that allows cluster administrators to observe the network traffic for {product-title} clusters. The Network Observability Operator uses the eBPF technology to create network flows. The network flows are then enriched with {product-title} information and stored in Loki. You can view and analyze the stored network flows information in the {product-title} console for further insight and troubleshooting. For more information, see xref:../network_observability/network-observability-overview.adoc#dependency-network-observability[About Network Observability Operator]. +The Network Observability Operator is an optional Operator that allows cluster administrators to observe the network traffic for {product-title} clusters. The Network Observability Operator uses the eBPF technology to create network flows. The network flows are then enriched with {product-title} information and stored in Loki. You can view and analyze the stored network flows information in the {product-title} console for further insight and troubleshooting. For more information, see xref:../observability/network_observability/network-observability-overview.adoc#dependency-network-observability[About Network Observability Operator]. diff --git a/observability/index.adoc b/observability/index.adoc index 0032dc4f24a8..0ff5c5f36ec1 100644 --- a/observability/index.adoc +++ b/observability/index.adoc @@ -52,8 +52,7 @@ For more information, see xref:otel/otel-installing.adoc#install-otel[{OTELName} == Network Observability Observe the network traffic for {product-title} clusters and create network flows with the Network Observability Operator. View and analyze the stored network flows information in the {product-title} console for further insight and troubleshooting. -For more information, see xref:../network_observability/network-observability-overview.adoc#network-observability-overview[Network Observability overview]. -//after the file is added to the observability directory, update xref path to ../observability/network_observability/network-observability-overview.adoc#network-observability-overview[Network Observability overview]. +For more information, see xref:../observability/network_observability/network-observability-overview.adoc#network-observability-overview[Network Observability overview]. [id="power-monitoring-overview-index"] == Power monitoring diff --git a/network_observability/_attributes b/observability/network_observability/_attributes similarity index 100% rename from network_observability/_attributes rename to observability/network_observability/_attributes diff --git a/network_observability/configuring-operator.adoc b/observability/network_observability/configuring-operator.adoc similarity index 67% rename from network_observability/configuring-operator.adoc rename to observability/network_observability/configuring-operator.adoc index 4f5ca571d2cb..f10351970fa5 100644 --- a/network_observability/configuring-operator.adoc +++ b/observability/network_observability/configuring-operator.adoc @@ -13,21 +13,21 @@ include::modules/network-observability-flowcollector-view.adoc[leveloffset=+1] [role="_additional-resources"] .Additional resources -For more information about conversation tracking, see xref:../network_observability/observing-network-traffic.adoc#network-observability-working-with-conversations_nw-observe-network-traffic[Working with conversations]. +For more information about conversation tracking, see xref:../../observability/network_observability/observing-network-traffic.adoc#network-observability-working-with-conversations_nw-observe-network-traffic[Working with conversations]. include::modules/network-observability-flowcollector-kafka-config.adoc[leveloffset=+1] include::modules/network-observability-enriched-flows.adoc[leveloffset=+1] [role="_additional-resources"] .Additional resources -For more information about specifying flow format, see xref:../network_observability/json-flows-format-reference.adoc#network-observability-flows-format_json_reference[Network flows format reference]. +For more information about specifying flow format, see xref:../../observability/network_observability/json-flows-format-reference.adoc#network-observability-flows-format_json_reference[Network flows format reference]. include::modules/network-observability-configuring-FLP-sampling.adoc[leveloffset=+1] include::modules/network-observability-configuring-quickfilters-flowcollector.adoc[leveloffset=+1] include::modules/network-observability-SRIOV-configuration.adoc[leveloffset=+1] [role="_additional-resources"] .Additional resources -For more information about creating the `SriovNetwork` custom resource, see 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]. +For more information about creating the `SriovNetwork` custom resource, see 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]. include::modules/network-observability-resource-recommendations.adoc[leveloffset=+1] include::modules/network-observability-resources-table.adoc[leveloffset=+2] \ No newline at end of file diff --git a/network_observability/flowcollector-api.adoc b/observability/network_observability/flowcollector-api.adoc similarity index 100% rename from network_observability/flowcollector-api.adoc rename to observability/network_observability/flowcollector-api.adoc diff --git a/network_observability/images b/observability/network_observability/images similarity index 100% rename from network_observability/images rename to observability/network_observability/images diff --git a/observability/network_observability/installing-operators.adoc b/observability/network_observability/installing-operators.adoc new file mode 100644 index 000000000000..4579d42f2132 --- /dev/null +++ b/observability/network_observability/installing-operators.adoc @@ -0,0 +1,67 @@ +:_mod-docs-content-type: ASSEMBLY +[id="installing-network-observability-operators"] += Installing the Network Observability Operator +include::_attributes/common-attributes.adoc[] +:context: network_observability + +toc::[] +Installing Loki is a recommended prerequisite for using the Network Observability Operator. You can choose to use xref:../../observability/network_observability/installing-operators.adoc#network-observability-without-loki_network_observability[Network Observability without Loki], but there are some considerations for doing this, described in the previously linked section. + +The {loki-op} integrates a gateway that implements multi-tenancy and authentication with Loki for data flow storage. The `LokiStack` resource manages Loki, which is a scalable, highly-available, multi-tenant log aggregation system, and a web proxy with {product-title} authentication. The `LokiStack` proxy uses {product-title} authentication to enforce multi-tenancy and facilitate the saving and indexing of data in Loki log stores. + +[NOTE] +==== +The {loki-op} can also be used for xref:../../logging/log_storage/cluster-logging-loki.adoc#cluster-logging-loki[configuring the LokiStack log store]. The Network Observability Operator requires a dedicated LokiStack separate from the {logging}. +==== + +include::modules/network-observability-without-loki.adoc[leveloffset=+1] + +[role="_additional-resources"] +.Additional resources +* xref:../../observability/network_observability/configuring-operator.adoc#network-observability-enriched-flows_network_observability[Export enriched network flow data]. + +include::modules/network-observability-loki-install.adoc[leveloffset=+1] +include::modules/network-observability-loki-secret.adoc[leveloffset=+2] +[role="_additional-resources"] +.Additional resources +* xref:../../observability/network_observability/flowcollector-api.adoc#network-observability-flowcollector-api-specifications_network_observability[Flow Collector API Reference] +* xref:../../observability/network_observability/configuring-operator.adoc#network-observability-flowcollector-view_network_observability[Flow Collector sample resource] +* xref:../../logging/log_storage/installing-log-storage.adoc#logging-loki-storage_installing-log-storage[Loki object storage] + +include::modules/network-observability-lokistack-create.adoc[leveloffset=+2] +include::modules/logging-creating-new-group-cluster-admin-user-role.adoc[leveloffset=+2] +include::modules/logging-loki-log-access.adoc[leveloffset=+1,tags=CustomAdmin;NetObservMode;!LokiMode] +include::modules/loki-deployment-sizing.adoc[leveloffset=+2] +include::modules/network-observability-lokistack-ingestion-query.adoc[leveloffset=+2] +include::modules/network-observability-multitenancy.adoc[leveloffset=+2] +include::modules/network-observability-operator-install.adoc[leveloffset=+1] + +[role="_additional-resources"] +[id="additional-resources_configuring-flow-collector-considerations"] +== Important Flow Collector configuration considerations +Once you create the `FlowCollector` instance, you can reconfigure it, but the pods are terminated and recreated again, which can be disruptive. Therefore, you can consider configuring the following options when creating the `FlowCollector` for the first time: + +* xref:../../observability/network_observability/configuring-operator.adoc#network-observability-flowcollector-kafka-config_network_observability[Configuring the Flow Collector resource with Kafka] +* xref:../../observability/network_observability/configuring-operator.adoc#network-observability-enriched-flows_network_observability[Export enriched network flow data to Kafka or IPFIX] +* xref:../../observability/network_observability/configuring-operator.adoc#network-observability-SR-IOV-config_network_observability[Configuring monitoring for SR-IOV interface traffic] +* xref:../../observability/network_observability/observing-network-traffic.adoc#network-observability-working-with-conversations_nw-observe-network-traffic[Working with conversation tracking] +* xref:../../observability/network_observability/observing-network-traffic.adoc#network-observability-dns-tracking_nw-observe-network-traffic[Working with DNS tracking] +* xref:../../observability/network_observability/observing-network-traffic.adoc#network-observability-packet-drops_nw-observe-network-traffic[Working with packet drops] + +[role="_additional-resources"] +.Additional resources +For more general information about Flow Collector specifications and the Network Observability Operator architecture and resource use, see the following resources: + +* xref:../../observability/network_observability/flowcollector-api.adoc#network-observability-flowcollector-api-specifications_network_observability[Flow Collector API Reference] +* xref:../../observability/network_observability/configuring-operator.adoc#network-observability-flowcollector-view_network_observability[Flow Collector sample resource] +* xref:../../observability/network_observability/configuring-operator.adoc#network-observability-resources-table_network_observability[Resource considerations] +* xref:../../observability/network_observability/troubleshooting-network-observability.adoc#controller-manager-pod-runs-out-of-memory_network-observability-troubleshooting[Troubleshooting Network Observability controller manager pod runs out of memory] +* xref:../../observability/network_observability/understanding-network-observability-operator.adoc#network-observability-architecture_nw-network-observability-operator[Network Observability architecture] + + +include::modules/network-observability-kafka-option.adoc[leveloffset=+1] +[role="_additional-resources"] +.Additional resources +xref:../../observability/network_observability/configuring-operator.adoc#network-observability-flowcollector-kafka-config_network_observability[Configuring the FlowCollector resource with Kafka]. + +include::modules/network-observability-operator-uninstall.adoc[leveloffset=+1] diff --git a/network_observability/json-flows-format-reference.adoc b/observability/network_observability/json-flows-format-reference.adoc similarity index 100% rename from network_observability/json-flows-format-reference.adoc rename to observability/network_observability/json-flows-format-reference.adoc diff --git a/network_observability/metrics-alerts-dashboards.adoc b/observability/network_observability/metrics-alerts-dashboards.adoc similarity index 80% rename from network_observability/metrics-alerts-dashboards.adoc rename to observability/network_observability/metrics-alerts-dashboards.adoc index 2c880161e29f..29426384b2ad 100644 --- a/network_observability/metrics-alerts-dashboards.adoc +++ b/observability/network_observability/metrics-alerts-dashboards.adoc @@ -14,4 +14,4 @@ include::modules/network-observability-includelist-example.adoc[leveloffset=+1] [role="_additional-resources"] .Additional resources -* For more information about creating alerts that you can see on the dashboard, see xref:../monitoring/managing-alerts.adoc#creating-alerting-rules-for-user-defined-projects_managing-alerts[Creating alerting rules for user-defined projects]. +* For more information about creating alerts that you can see on the dashboard, see xref:../../monitoring/managing-alerts.adoc#creating-alerting-rules-for-user-defined-projects_managing-alerts[Creating alerting rules for user-defined projects]. diff --git a/network_observability/modules b/observability/network_observability/modules similarity index 100% rename from network_observability/modules rename to observability/network_observability/modules diff --git a/network_observability/network-observability-network-policy.adoc b/observability/network_observability/network-observability-network-policy.adoc similarity index 78% rename from network_observability/network-observability-network-policy.adoc rename to observability/network_observability/network-observability-network-policy.adoc index 3cd8e3361cb1..db71ea6045ca 100644 --- a/network_observability/network-observability-network-policy.adoc +++ b/observability/network_observability/network-observability-network-policy.adoc @@ -13,4 +13,4 @@ include::modules/network-observability-sample-network-policy-YAML.adoc[leveloffs [role="_additional-resources"] .Additional resources -xref:../networking/network_policy/creating-network-policy.adoc#nw-networkpolicy-object_creating-network-policy[Creating a network policy using the CLI] \ No newline at end of file +xref:../../networking/network_policy/creating-network-policy.adoc#nw-networkpolicy-object_creating-network-policy[Creating a network policy using the CLI] \ No newline at end of file diff --git a/network_observability/network-observability-operator-monitoring.adoc b/observability/network_observability/network-observability-operator-monitoring.adoc similarity index 79% rename from network_observability/network-observability-operator-monitoring.adoc rename to observability/network_observability/network-observability-operator-monitoring.adoc index 226174cea76e..513a6b12042b 100644 --- a/network_observability/network-observability-operator-monitoring.adoc +++ b/observability/network_observability/network-observability-operator-monitoring.adoc @@ -15,4 +15,4 @@ include::modules/network-observability-rate-limit-alert.adoc[leveloffset=+1] [role="_additional-resources"] .Additional resources -* For more information about creating alerts that you can see on the dashboard, see xref:../monitoring/managing-alerts.adoc#creating-alerting-rules-for-user-defined-projects_managing-alerts[Creating alerting rules for user-defined projects]. \ No newline at end of file +* For more information about creating alerts that you can see on the dashboard, see xref:../../monitoring/managing-alerts.adoc#creating-alerting-rules-for-user-defined-projects_managing-alerts[Creating alerting rules for user-defined projects]. \ No newline at end of file diff --git a/network_observability/network-observability-operator-release-notes.adoc b/observability/network_observability/network-observability-operator-release-notes.adoc similarity index 86% rename from network_observability/network-observability-operator-release-notes.adoc rename to observability/network_observability/network-observability-operator-release-notes.adoc index 1466c3076c44..a32195272a3c 100644 --- a/network_observability/network-observability-operator-release-notes.adoc +++ b/observability/network_observability/network-observability-operator-release-notes.adoc @@ -11,7 +11,7 @@ The Network Observability Operator enables administrators to observe and analyze These release notes track the development of the Network Observability Operator in the {product-title}. -For an overview of the Network Observability Operator, see xref:../network_observability/network-observability-overview.adoc#dependency-network-observability[About Network Observability Operator]. +For an overview of the Network Observability Operator, see xref:../../observability/network_observability/network-observability-overview.adoc#dependency-network-observability[About Network Observability Operator]. [id="network-observability-operator-release-notes-1-5"] == Network Observability Operator 1.5.0 @@ -24,23 +24,23 @@ The following advisory is available for the Network Observability Operator 1.5.0 [id="network-observability-dns-enhancements-1.5"] ==== 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:../network_observability/observing-network-traffic.adoc#network-observability-dns-overview_nw-observe-network-traffic[Configuring DNS tracking] and xref:../network_observability/observing-network-traffic.adoc#network-observability-dns-tracking_nw-observe-network-traffic[Working with DNS tracking]. +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]. [id="network-observability-RTT-1.5"] ==== 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:../network_observability/observing-network-traffic.adoc#network-observability-RTT-overview_nw-observe-network-traffic[RTT Overview] and xref:../network_observability/observing-network-traffic.adoc#network-observability-RTT_nw-observe-network-traffic[Working with 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]. [id="network-observability-metrics-dashboard-enhancements"] ==== 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:../network_observability/metrics-alerts-dashboards.adoc#network-observability-metrics_metrics-dashboards-alerts[Network Observability Metrics]. +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]. [id="network-observability-improved-lokistack-integration"] ==== 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:../network_observability/metrics-alerts-dashboards.adoc#network-observability-metrics_metrics-dashboards-alerts[Network Observability Metrics]. +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]. [id="network-observability-zones"] ==== 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:../network_observability/observing-network-traffic.adoc#network-observability-zonesnw-observe-network-traffic[Working with 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-zonesnw-observe-network-traffic[Working with availability zones]. [id="network-observability-enhanced-configuration-and-ui-1.5"] ==== Notable enhancements @@ -159,7 +159,7 @@ 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:../network_observability/network-observability-overview.adoc#network-observability-dashboards[Network Observability metrics] and xref:../network_observability/observing-network-traffic.adoc#network-observability-quickfilternw-observe-network-traffic[Quick filters]. +For more information, see xref:../../observability/network_observability/network-observability-overview.adoc#network-observability-dashboards[Network Observability metrics] and xref:../../observability/network_observability/observing-network-traffic.adoc#network-observability-quickfilternw-observe-network-traffic[Quick filters]. [discrete] [id="configuration-enhancements-1.4_{context}"] @@ -168,38 +168,38 @@ For more information, see xref:../network_observability/network-observability-ov * 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 xref:../network_observability/configuring-operator.adoc#network-observability-flowcollector-view_network_observability[Flow Collector sample resource] and xref:../network_observability/flowcollector-api.adoc#network-observability-flowcollector-api-specifications_network_observability[Flow Collector API Reference]. +For more information, see xref:../../observability/network_observability/configuring-operator.adoc#network-observability-flowcollector-view_network_observability[Flow Collector sample resource] and 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"] ==== 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 xref:../network_observability/installing-operators.adoc#network-observability-without-loki_network_observability[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 xref:../../observability/network_observability/installing-operators.adoc#network-observability-without-loki_network_observability[Network Observability without Loki]. [id="network-observability-dns-tracking-1.4"] ==== 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 xref:../network_observability/observing-network-traffic.adoc#network-observability-dns-overview_nw-observe-network-traffic[Configuring DNS tracking] and xref:../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] and 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"] ==== 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:../network_observability/configuring-operator.adoc#network-observability-SR-IOV-config_network_observability[Configuring the monitoring of SR-IOV interface traffic]. +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/configuring-operator.adoc#network-observability-SR-IOV-config_network_observability[Configuring the monitoring of SR-IOV interface traffic]. [id="IPFIX-support-1.4"] ==== IPFIX exporter support -You can now export eBPF-enriched network flows to the IPFIX collector. For more information, see xref:../network_observability/configuring-operator.adoc#network-observability-enriched-flows_network_observability[Export enriched network flow data]. +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]. [id="network-observability-packet-drop-1.4"] ==== 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:../network_observability/observing-network-traffic#network-observability-pktdrop-overview_nw-observe-network-traffic[Configuring packet drop tracking] and xref:../network_observability/observing-network-traffic#network-observability-packet-drops_nw-observe-network-traffic[Working with 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#network-observability-pktdrop-overview_nw-observe-network-traffic[Configuring packet drop tracking] and xref:../../observability/network_observability/observing-network-traffic#network-observability-packet-drops_nw-observe-network-traffic[Working with packet drops]. ==== s390x architecture support Network Observability Operator can now run on `s390x` architecture. Previously it ran on `amd64`, `ppc64le`, or `arm64`. [id="network-observability-operator-1.4.0-bug-fixes"] === Bug fixes -* Previously, the Prometheus metrics exported by Network Observability were computed out of potentially duplicated network flows. In the related dashboards, from *Observe* -> *Dashboards*, this could result in potentially doubled rates. Note that dashboards from the *Network Traffic* view were not affected. Now, network flows are filtered to eliminate duplicates prior to metrics calculation, which results in correct traffic rates displayed in the dashboards. (link:https://issues.redhat.com/browse/NETOBSERV-1131[*NETOBSERV-1131*]) +* Previously, the Prometheus metrics exported by Network Observability were computed out of potentially duplicated network flows. In the related dashboards, from *Observe* -> *Dashboards*, this could result in potentially doubled rates. Note that dashboards from the *Network Traffic* view were not affected. Now, network flows are filtered to eliminate duplicates before metrics calculation, which results in correct traffic rates displayed in the dashboards. (link:https://issues.redhat.com/browse/NETOBSERV-1131[*NETOBSERV-1131*]) -* Previously, the Network Observability Operator agents were not able to capture traffic on network interfaces when configured with Multus or SR-IOV, non-default network namespaces. Now, all available network namespaces are recognized and used for capturing flows, allowing capturing traffic for SR-IOV. There are xref:../network_observability/configuring-operator.adoc#network-observability-SR-IOV-config_network_observability[configurations needed] for the `FlowCollector` and `SRIOVnetwork` custom resource to collect traffic. +* Previously, the Network Observability Operator agents were not able to capture traffic on network interfaces when configured with Multus or SR-IOV, non-default network namespaces. Now, all available network namespaces are recognized and used for capturing flows, allowing capturing traffic for SR-IOV. There are xref:../../observability/network_observability/configuring-operator.adoc#network-observability-SR-IOV-config_network_observability[configurations needed] for the `FlowCollector` and `SRIOVnetwork` custom resource to collect traffic. (link:https://issues.redhat.com/browse/NETOBSERV-1283[*NETOBSERV-1283*]) * Previously, in the Network Observability Operator details from *Operators* -> *Installed Operators*, the `FlowCollector` *Status* field might have reported incorrect information about the state of the deployment. The status field now shows the proper conditions with improved messages. The history of events is kept, ordered by event date. (link:https://issues.redhat.com/browse/NETOBSERV-1224[*NETOBSERV-1224*]) @@ -237,15 +237,15 @@ You must switch your channel from `v1.0.x` to `stable` to receive future Operato [id="multi-tenancy-1.3"] ==== Multi-tenancy in Network Observability -* System administrators can allow and restrict individual user access, or group access, to the flows stored in Loki. For more information, see xref:../network_observability/installing-operators.adoc#network-observability-multi-tenancynetwork_observability[Multi-tenancy in Network Observability]. +* System administrators can allow and restrict individual user access, or group access, to the flows stored in Loki. For more information, see xref:../../observability/network_observability/installing-operators.adoc#network-observability-multi-tenancynetwork_observability[Multi-tenancy in Network Observability]. [id="flow-based-dashboard-1.3"] ==== Flow-based metrics dashboard -* This release adds a new dashboard, which provides an overview of the network flows in your {product-title} cluster. For more information, see xref:../network_observability/network-observability-overview.adoc#network-observability-dashboards[Network Observability metrics]. +* This release adds a new dashboard, which provides an overview of the network flows in your {product-title} cluster. For more information, see xref:../../observability/network_observability/network-observability-overview.adoc#network-observability-dashboards[Network Observability metrics]. [id="must-gather-1.3"] ==== Troubleshooting with the must-gather tool -* Information about the Network Observability Operator can now be included in the must-gather data for troubleshooting. For more information, see xref:../network_observability/troubleshooting-network-observability.adoc#network-observability-must-gather_network-observability-troubleshooting[Network Observability must-gather]. +* Information about the Network Observability Operator can now be included in the must-gather data for troubleshooting. For more information, see xref:../../observability/network_observability/troubleshooting-network-observability.adoc#network-observability-must-gather_network-observability-troubleshooting[Network Observability must-gather]. [id="multi-arch-1.3"] ==== Multiple architectures now supported @@ -299,15 +299,15 @@ The subscription of an installed Operator specifies an update channel that track [id="histogram-feature-1.2"] ==== Histogram in Traffic Flows view -* You can now choose to show a histogram bar chart of flows over time. The histogram enables you to visualize the history of flows without hitting the Loki query limit. For more information, see xref:../network_observability/observing-network-traffic.adoc#network-observability-histogram-trafficflow_nw-observe-network-traffic[Using the histogram]. +* You can now choose to show a histogram bar chart of flows over time. The histogram enables you to visualize the history of flows without hitting the Loki query limit. For more information, see xref:../../observability/network_observability/observing-network-traffic.adoc#network-observability-histogram-trafficflow_nw-observe-network-traffic[Using the histogram]. [id="conversation-tracking-feature-1.2"] ==== Conversation tracking -* You can now query flows by *Log Type*, which enables grouping network flows that are part of the same conversation. For more information, see xref:../network_observability/observing-network-traffic.adoc#network-observability-working-with-conversations_nw-observe-network-traffic[Working with conversations]. +* You can now query flows by *Log Type*, which enables grouping network flows that are part of the same conversation. For more information, see xref:../../observability/network_observability/observing-network-traffic.adoc#network-observability-working-with-conversations_nw-observe-network-traffic[Working with conversations]. [id="health-alerts-feature-1.2"] ==== Network Observability health alerts -* The Network Observability Operator now creates automatic alerts if the `flowlogs-pipeline` is dropping flows because of errors at the write stage or if the Loki ingestion rate limit has been reached. For more information, see xref:../network_observability/network-observability-operator-monitoring.adoc#network-observability-alert-dashboard_network_observability[Viewing health information]. +* The Network Observability Operator now creates automatic alerts if the `flowlogs-pipeline` is dropping flows because of errors at the write stage or if the Loki ingestion rate limit has been reached. For more information, see xref:../../observability/network_observability/network-observability-operator-monitoring.adoc#network-observability-alert-dashboard_network_observability[Viewing health information]. [id="network-observability-operator-1.2.0-bug-fixes"] === Bug fixes diff --git a/network_observability/network-observability-overview.adoc b/observability/network_observability/network-observability-overview.adoc similarity index 100% rename from network_observability/network-observability-overview.adoc rename to observability/network_observability/network-observability-overview.adoc diff --git a/network_observability/observing-network-traffic.adoc b/observability/network_observability/observing-network-traffic.adoc similarity index 68% rename from network_observability/observing-network-traffic.adoc rename to observability/network_observability/observing-network-traffic.adoc index f7549b4428c9..6c4268c3876d 100644 --- a/network_observability/observing-network-traffic.adoc +++ b/observability/network_observability/observing-network-traffic.adoc @@ -16,21 +16,21 @@ include::modules/network-observability-pktdrop-overview.adoc[leveloffset=+2] [role="_additional-resources"] .Additional resources -* xref:../network_observability/observing-network-traffic.adoc#network-observability-packet-drops_nw-observe-network-traffic[Working with packet drops] -* xref:../network_observability/metrics-alerts-dashboards.adoc#network-observability-metrics_metrics-dashboards-alerts[Network Observability metrics] +* xref:../../observability/network_observability/observing-network-traffic.adoc#network-observability-packet-drops_nw-observe-network-traffic[Working with packet drops] +* xref:../../observability/network_observability/metrics-alerts-dashboards.adoc#network-observability-metrics_metrics-dashboards-alerts[Network Observability metrics] include::modules/network-observability-dns-overview.adoc[leveloffset=+2] [role="_additional-resources"] .Additional resources -* xref:../network_observability/observing-network-traffic.adoc#network-observability-dns-tracking_nw-observe-network-traffic[Working with DNS tracking] -* xref:../network_observability/metrics-alerts-dashboards.adoc#network-observability-metrics_metrics-dashboards-alerts[Network Observability metrics] +* xref:../../observability/network_observability/observing-network-traffic.adoc#network-observability-dns-tracking_nw-observe-network-traffic[Working with DNS tracking] +* xref:../../observability/network_observability/metrics-alerts-dashboards.adoc#network-observability-metrics_metrics-dashboards-alerts[Network Observability metrics] include::modules/network-observability-RTT-overview.adoc[leveloffset=+2] [role="_additional-resources"] .Additional resources -* xref:../network_observability/observing-network-traffic.adoc#network-observability-RTT_nw-observe-network-traffic[Working with RTT tracing] +* xref:../../observability/network_observability/observing-network-traffic.adoc#network-observability-RTT_nw-observe-network-traffic[Working with RTT tracing] //Traffic flows include::modules/network-observability-trafficflow.adoc[leveloffset=+1] @@ -55,4 +55,4 @@ Alternatively, you can access the traffic flow data in the *Network Traffic* tab [role="_additional-resources"] .Additional resources -For more information about configuring quick filters in the `FlowCollector`, see xref:../network_observability/configuring-operator.adoc#network-observability-config-quick-filters_network_observability[Configuring Quick Filters] and the xref:../network_observability/configuring-operator.adoc#network-observability-flowcollector-view_network_observability[Flow Collector sample resource]. +For more information about configuring quick filters in the `FlowCollector`, see xref:../../observability/network_observability/configuring-operator.adoc#network-observability-config-quick-filters_network_observability[Configuring Quick Filters] and the xref:../../observability/network_observability/configuring-operator.adoc#network-observability-flowcollector-view_network_observability[Flow Collector sample resource]. diff --git a/network_observability/snippets b/observability/network_observability/snippets similarity index 100% rename from network_observability/snippets rename to observability/network_observability/snippets diff --git a/network_observability/troubleshooting-network-observability.adoc b/observability/network_observability/troubleshooting-network-observability.adoc similarity index 88% rename from network_observability/troubleshooting-network-observability.adoc rename to observability/network_observability/troubleshooting-network-observability.adoc index fdb03d8ebd9c..af19012d8dfb 100644 --- a/network_observability/troubleshooting-network-observability.adoc +++ b/observability/network_observability/troubleshooting-network-observability.adoc @@ -20,7 +20,7 @@ include::modules/troubleshooting-network-observability-controller-manager-pod-ou [role="_additional-resources"] .Additional resources -* xref:../network_observability/configuring-operator.adoc#network-observability-resources-table_network_observability[Resource considerations] +* xref:../../observability/network_observability/configuring-operator.adoc#network-observability-resources-table_network_observability[Resource considerations] include::modules/troubleshooting-network-observability-loki-resource-exhausted.adoc[leveloffset=+1] include::modules/troubleshooting-network-observability-loki-empty-ring.adoc[leveloffset=+1] diff --git a/network_observability/understanding-network-observability-operator.adoc b/observability/network_observability/understanding-network-observability-operator.adoc similarity index 100% rename from network_observability/understanding-network-observability-operator.adoc rename to observability/network_observability/understanding-network-observability-operator.adoc diff --git a/welcome/index.adoc b/welcome/index.adoc index 40b96d43578b..b83829e8d441 100644 --- a/welcome/index.adoc +++ b/welcome/index.adoc @@ -295,8 +295,7 @@ Use the Cluster Version Operator (CVO) to upgrade your {product-title} cluster. // xreffing to the installation page until further notice because OTEL content is currently planned for internal restructuring across pages that is likely to result in renamed page files - **xref:../observability/otel/otel-installing.adoc#install-otel[Red Hat build of OpenTelemetry]**: Instrument, generate, collect, and export telemetry traces, metrics, and logs to analyze and understand your software's performance and behavior. Use open source backends like Tempo or Prometheus, or use commercial offerings. Learn a single set of APIs and conventions, and own the data that you generate. -// CHECK IN CLOSER TO THE GA DATE BECAUSE FEATURE WORK IS NOT MERGED; ESTIMATED MERGE BY 19 FEB. ADD xref:../network_observability/metrics-alerts-dashboards.adoc#network-observability-viewing-dashboards_metrics-dashboards-alerts to [view dashbaords text. -- **xref:../network_observability/network-observability-overview.adoc#network-observability-overview[Network Observability]**: Observe network traffic for {product-title} clusters by using eBPF technology to create and enrich network flows. You can xref:../network_observability/metrics-alerts-dashboards.adoc#metrics-alerts-dashboards_metrics-alerts-dashboards[view dashboards, customize alerts], and xref:../network_observability/observing-network-traffic.adoc#network-observability-trafficflow_nw-observe-network-traffic[analyze network flow] information for further insight and troubleshooting. +- **xref:../observability/network_observability/network-observability-overview.adoc#network-observability-overview[Network Observability]**: Observe network traffic for {product-title} clusters by using eBPF technology to create and enrich network flows. You can xref:../observability/network_observability/metrics-alerts-dashboards.adoc#metrics-alerts-dashboards_metrics-alerts-dashboards[view dashboards, customize alerts], and xref:../observability/network_observability/observing-network-traffic.adoc#network-observability-trafficflow_nw-observe-network-traffic[analyze network flow] information for further insight and troubleshooting. - **xref:../monitoring/monitoring-overview.adoc#monitoring-overview[In-cluster monitoring]**: Learn to xref:../monitoring/configuring-the-monitoring-stack.adoc#configuring-the-monitoring-stack[configure the monitoring stack].