openshift/openshift-docs
1
0
Fork 0
mirror of https://github.com/openshift/openshift-docs.git synced 2026-02-05 12:46:18 +01:00
Code Issues Releases Activity

OSDOCS-OSDOCS-10656:Updating Network Observability arch Loki-less option

Browse Source
This commit is contained in:
Sara Thomas
2024-08-12 16:53:21 -04:00
committed by openshift-cherrypick-robot
parent 7def8ddc27
commit ffc2ab914a
4 changed files with 8 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

BIN
images/network-observability-arch-kafka-FLP.png
View File

Binary file not shown.
Side by Side Swipe Overlay

Before

Width:  |  Height:  |  Size: 130 KiB

After

Width:  |  Height:  |  Size: 135 KiB

BIN
images/network-observability-architecture.png
View File

Binary file not shown.
Side by Side Swipe Overlay

Before

Width:  |  Height:  |  Size: 127 KiB

After

Width:  |  Height:  |  Size: 132 KiB

4
modules/network-observability-architecture.adoc
View File

@@ -8,7 +8,9 @@
The Network Observability Operator provides the `FlowCollector` API, which is instantiated at installation and configured to reconcile the `eBPF agent`, the `flowlogs-pipeline`, and the `netobserv-plugin` components. Only a single `FlowCollector` per cluster is supported.
The `eBPF agent` runs on each cluster node with some privileges to collect network flows. The `flowlogs-pipeline` receives the network flows data and enriches the data with Kubernetes identifiers. If you are using Loki, the `flowlogs-pipeline` sends flow logs data to Loki for storing and indexing. The `netobserv-plugin`, which is a dynamic {product-title} web console plugin, queries Loki to fetch network flows data. Cluster-admins can view the data in the web console.
The `eBPF agent` runs on each cluster node with some privileges to collect network flows. The `flowlogs-pipeline` receives the network flows data and enriches the data with Kubernetes identifiers. If you choose to use Loki, the `flowlogs-pipeline` sends flow logs data to Loki for storing and indexing. The `netobserv-plugin`, which is a dynamic {product-title} web console plugin, queries Loki to fetch network flows data. Cluster-admins can view the data in the web console.
If you do not use Loki, you can generate metrics with Prometheus. Those metrics and their related dashboards are accessible in the web console. For more information, see "Network Observability without Loki".
image::network-observability-architecture.png[Network Observability eBPF export architecture]

5
observability/network_observability/understanding-network-observability-operator.adoc
View File

@@ -10,4 +10,9 @@ Network Observability is an OpenShift operator that deploys a monitoring pipelin
include::modules/nw-network-observability-operator.adoc[leveloffset=+1]
include::modules/network-observability-architecture.adoc[leveloffset=+1]
[role="_additional-resources"]
.Additional resources
* xref:../network_observability/installing-operators.adoc#network-observability-without-loki_network_observability[Network Observability without Loki]
include::modules/nw-view-status-configuration-network-observability-operator.adoc[leveloffset=+1]