Skip to content

Commit b111af3

Browse files
committed
OSDOCS-11625:Viewing Network events in Network Observability
1 parent 6e028b5 commit b111af3

File tree

3 files changed

+79
-0
lines changed

3 files changed

+79
-0
lines changed
Lines changed: 12 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,12 @@
1+
// Module included in the following assemblies:
2+
//
3+
// network_observability/observing-network-traffic.adoc
4+
5+
:_mod-docs-content-type: CONCEPT
6+
[id="network-observability-networking-events-overview_{context}"]
7+
= OVN Kubernetes networking events
8+
You use network event tracking in Network Observability to gain insight into OVN-Kubernetes events, including network policies, admin network policies, and egress firewalls. You can use the insights from tracking network events to help with the following:
9+
10+
* Network monitoring: Monitor allowed and blocked traffic, detecting whether packets are allowed or blocked based on network policies and admin network policies.
11+
12+
* Network security: You can track outbound traffic and see whether it adheres to egress firewall rules. Detect unauthorized outbound connections and flag outbound traffic that violates egress rules.
Lines changed: 57 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,57 @@
1+
// Module included in the following assemblies:
2+
//
3+
// * network_observability/observing-network-traffic.adoc
4+
5+
:_mod-docs-content-type: PROCEDURE
6+
[id="network-observability-viewing-network-events_{context}"]
7+
= Viewing network events
8+
You can view network events, such as network flows that are dropped or allowed by a network policy, by editing the `FlowCollector` to the specifications in the following YAML example.
9+
10+
.Prerequisites
11+
* Must have the `OVNObservability` specified in the `FeatureGate` custom resource. For more information, see "Enabling features using feature gates" in the "Additional resources" of this section.
12+
13+
.Procedure
14+
. In the web console, navigate to *Operators* -> *Installed Operators*.
15+
. In the *Provided APIs* heading for the *NetObserv Operator*, select *Flow Collector*.
16+
. Select *cluster*, and then select the *YAML* tab.
17+
. Configure the `FlowCollector` custom resource to enable viewing `NetworkEvents`, for example:
18+
+
19+
[id="network-observability-flowcollector-configuring-networkevents{context}"]
20+
.Example `FlowCollector` configuration
21+
[source, yaml]
22+
----
23+
apiVersion: flows.netobserv.io/v1beta2
24+
kind: FlowCollector
25+
metadata:
26+
name: cluster
27+
spec:
28+
agent:
29+
type: eBPF
30+
ebpf:
31+
sampling: 1 <1>
32+
privileged: true <2>
33+
features:
34+
- "NetworkEvents"
35+
----
36+
<1> The `sampling` parameter is set to a value of 1 so that all network events are captured.
37+
<2> The `privileged` parameter is set to `true` because the `OVN observability` library needs to access local OVS socket and OVN databases
38+
39+
.Verification
40+
. Navigate to the *Network Traffic* view and select the *Traffic flows* table.
41+
. You should see the new column, *Network Events*, where you can view information about impacts that network policies, admin policies, and egress firewalls have on network flows.
42+
+
43+
.Examples of Network Events output
44+
[source,text]
45+
----
46+
Dropped by cluster multicast policy, direction Ingress
47+
----
48+
+
49+
[source,text]
50+
----
51+
Allowed by network policy iperf.iperf3-server-access-egress, direction Egress
52+
----
53+
+
54+
[source,text]
55+
----
56+
Allowed by admin network policy allow-egress-iperf, direction Egress
57+
----

observability/network_observability/observing-network-traffic.adoc

Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -41,6 +41,11 @@ include::modules/network-observability-flow-filter-parameters.adoc[leveloffset=+
4141
* xref:../../observability/network_observability/metrics-alerts-dashboards.adoc#network-observability-metrics_metrics-dashboards-alerts[Network Observability metrics]
4242
* xref:../../observability/network_observability/network-observability-operator-monitoring.adoc#network-observability-health-dashboard-overview_network_observability[Health dashboards]
4343
44+
include::modules/network-observability-networking-events-overview.adoc[leveloffset=+2]
45+
[role="_additional-resources"]
46+
.Additional resources
47+
* xref:../../observability/network_observability/observing-network-traffic.adoc#network-observability-viewing-network-events_nw-observe-network-traffic[Viewing network events]
48+
4449
//Traffic flows
4550
include::modules/network-observability-trafficflow.adoc[leveloffset=+1]
4651
include::modules/network-observability-working-with-trafficflow.adoc[leveloffset=+2]
@@ -52,6 +57,11 @@ include::modules/network-observability-RTT.adoc[leveloffset=+2]
5257
include::modules/network-observability-histogram-trafficflow.adoc[leveloffset=+2]
5358
include::modules/network-observability-working-with-zones.adoc[leveloffset=+2]
5459
include::modules/network-observability-filtering-ebpf-rule.adoc[leveloffset=+2]
60+
include::modules/network-observability-viewing-network-events.adoc[leveloffset=+2]
61+
62+
[role="_additional-resources"]
63+
.Additional resources
64+
* Placeholder for link to OVN-K topic on `OVNObservability`
5565
5666
//Topology
5767
include::modules/network-observability-topology.adoc[leveloffset=+1]

0 commit comments

Comments
 (0)