Merge pull request #53360 from xenolinux/netobserv-overview

OSDOCS#4603: Adds the overview page for Network Observability

Author: snarayan-redhat

_topic_maps/_topic_map.yml

@@ -1311,6 +1311,8 @@ Topics:
 - Name: Network Observability
   Dir: network_observability
   Topics:
+  - Name: Network Observability overview
+    File: network-observability-overview
   - Name: Installing Network Observability operators
     File: installing-operators
   - Name: Observing the network traffic

networking/network_observability/network-observability-overview.adoc

@@ -0,0 +1,50 @@
+:_content-type: ASSEMBLY
+[id="network-observability-overview"]
+= About Network Observability
+include::_attributes/common-attributes.adoc[]
+:context: network-observability-overview
+
+toc::[]
+
+Red Hat offers cluster administrators the Network Observability Operator to observe the network traffic for {product-title} clusters. The Network Observability 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 netflow information in the {product-title} console for further insight and troubleshooting.
+
+[id="dependency-network-observability"]
+== Dependency of Network Observability Operator
+
+The Network Observability Operator requires the following Operators:
+
+* Loki: You must install Loki. Loki is the backend that is used to store all collected flows. It is recommended to install Loki by installing the Red Hat Loki Operator for the installation of Network Observability Operator.
+
+[id="optional-dependency-network-observability"]
+== Optional dependencies of the Network Observability Operator
+
+* Grafana: You can install Grafana for using custom dashboards and querying capabilities, by using the Grafana Operator. Red Hat does not support Grafana Operator.
+* Kafka: It provides scalability, resiliency and high availability in the {product-title} cluster. It is recommended to install Kafka using the AMQ Streams operator for large scale deployments.
+
+[id="network-observability-operator"]
+== Network Observability Operator
+
+The Network Observability Operator deploys a monitoring pipeline to collect and enrich the network flows. The eBPF agent, which is deployed as a `daemonset` object, creates the network flows. The network flows are then collected and enriched with the Kubernetes metadata, before storing in Loki.
+
+[id="no-console-integration"]
+== {product-title} console integration
+
+{product-title} console integration offers overview, topology view and traffic flow tables.
+
+[id="network-observability-dashboards"]
+=== Network Observability metrics
+
+By using Network Observability metrics, you can refine the stats by using the filters and display options. The {product-title} console offers the *Overview* tab which displays the overall aggregated metrics of the network traffic flow on the cluster. You can access the information for node, namespace, owner, pod, and service.
+
+[id="network-observability-topology-views"]
+=== Network Observability topology views
+
+The {product-title} console offers the *Topology* tab which displays a graphical representation of the network flows and the amount of traffic. The topology view represents traffic between the {product-title} components as a network graph. You can refine the graph by using the filters and display options. You can access the information for node, namespace, owner, pod, and service.
+
+[id="traffic-flow-tables"]
+=== Traffic flow tables
+
+The traffic flow table view provides a view for raw flows, non aggregated filtering options, and configurable columns. The {product-title} console offers the *Traffic flows* tab which displays the data of the network flows and the amount of traffic.
+
+
+