diff --git a/images/network-observability-arch-kafka-FLP.png b/images/network-observability-arch-kafka-FLP.png
index 7451e6111a..8b1765d634 100644
Binary files a/images/network-observability-arch-kafka-FLP.png and b/images/network-observability-arch-kafka-FLP.png differ
diff --git a/images/network-observability-architecture.png b/images/network-observability-architecture.png
index f1f89e31d1..4af1b4d9d4 100644
Binary files a/images/network-observability-architecture.png and b/images/network-observability-architecture.png differ
diff --git a/modules/network-observability-architecture.adoc b/modules/network-observability-architecture.adoc
index 3dd454a7e1..c6e22661d4 100644
--- a/modules/network-observability-architecture.adoc
+++ b/modules/network-observability-architecture.adoc
@@ -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]
 
diff --git a/observability/network_observability/understanding-network-observability-operator.adoc b/observability/network_observability/understanding-network-observability-operator.adoc
index a6176bad84..e104715c82 100644
--- a/observability/network_observability/understanding-network-observability-operator.adoc
+++ b/observability/network_observability/understanding-network-observability-operator.adoc
@@ -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]
\ No newline at end of file