// Module included in the following assemblies: // * networking/network_observability/understanding-network-observability-operator.adoc :_mod-docs-content-type: PROCEDURE [id="nw-network-observability-operator_{context}"] = Viewing statuses [role="_abstract"] View the operational status of the Network Observability Operator by using the `oc get` command to check the `FlowCollector` resource status, as well as the status of the `eBPF agent`, `flowlogs-pipeline`, and console plugin Pods. The Network Observability Operator provides the Flow Collector API. When a Flow Collector resource is created, it deploys pods and services to create and store network flows in the Loki log store, as well as to display dashboards, metrics, and flows in the {product-title} web console. .Procedure . Run the following command to view the state of `FlowCollector`: + [source,terminal] ---- $ oc get flowcollector/cluster ---- + .Example output ---- NAME AGENT SAMPLING (EBPF) DEPLOYMENT MODEL STATUS cluster EBPF 50 DIRECT Ready ---- . Check the status of pods running in the `netobserv` namespace by entering the following command: + [source,terminal] ---- $ oc get pods -n netobserv ---- + .Example output ---- NAME READY STATUS RESTARTS AGE flowlogs-pipeline-56hbp 1/1 Running 0 147m flowlogs-pipeline-9plvv 1/1 Running 0 147m flowlogs-pipeline-h5gkb 1/1 Running 0 147m flowlogs-pipeline-hh6kf 1/1 Running 0 147m flowlogs-pipeline-w7vv5 1/1 Running 0 147m netobserv-plugin-cdd7dc6c-j8ggp 1/1 Running 0 147m ---- + The `flowlogs-pipeline` pods collect flows, enriches the collected flows, then send flows to the Loki storage. `netobserv-plugin` pods create a visualization plugin for the {product-title} Console. . Check the status of pods running in the namespace `netobserv-privileged` by entering the following command: + [source,terminal] ---- $ oc get pods -n netobserv-privileged ---- + .Example output ---- NAME READY STATUS RESTARTS AGE netobserv-ebpf-agent-4lpp6 1/1 Running 0 151m netobserv-ebpf-agent-6gbrk 1/1 Running 0 151m netobserv-ebpf-agent-klpl9 1/1 Running 0 151m netobserv-ebpf-agent-vrcnf 1/1 Running 0 151m netobserv-ebpf-agent-xf5jh 1/1 Running 0 151m ---- + The `netobserv-ebpf-agent` pods monitor network interfaces of the nodes to get flows and send them to `flowlogs-pipeline` pods. . If you are using the {loki-op}, check the status of the `component` pods of `LokiStack` custom resource in the `netobserv` namespace by entering the following command: + [source,terminal] ---- $ oc get pods -n netobserv ---- + .Example output ---- NAME READY STATUS RESTARTS AGE lokistack-compactor-0 1/1 Running 0 18h lokistack-distributor-654f87c5bc-qhkhv 1/1 Running 0 18h lokistack-distributor-654f87c5bc-skxgm 1/1 Running 0 18h lokistack-gateway-796dc6ff7-c54gz 2/2 Running 0 18h lokistack-index-gateway-0 1/1 Running 0 18h lokistack-index-gateway-1 1/1 Running 0 18h lokistack-ingester-0 1/1 Running 0 18h lokistack-ingester-1 1/1 Running 0 18h lokistack-ingester-2 1/1 Running 0 18h lokistack-querier-66747dc666-6vh5x 1/1 Running 0 18h lokistack-querier-66747dc666-cjr45 1/1 Running 0 18h lokistack-querier-66747dc666-xh8rq 1/1 Running 0 18h lokistack-query-frontend-85c6db4fbd-b2xfb 1/1 Running 0 18h lokistack-query-frontend-85c6db4fbd-jm94f 1/1 Running 0 18h ----