mirror of
https://github.com/openshift/openshift-docs.git
synced 2026-02-05 21:46:22 +01:00
OSDOCS-15808 [NETOBSERV] Aditi tool results: RelatedLinks
This commit is contained in:
Gwynne Monahan
@@ -6,7 +6,9 @@
|
||||
[id="network-observability-quickfilter_{context}"]
|
||||
= Filtering the network traffic
|
||||
|
||||
By default, the Network Traffic page displays the traffic flow data in the cluster based on the default filters configured in the `FlowCollector` instance. You can use the filter options to observe the required data by changing the preset filter.
|
||||
By default, the *Network Traffic* page displays the traffic flow data in the cluster based on the default filters configured in the `FlowCollector` instance. You can use the filter options to observe the required data by changing the preset filter.
|
||||
|
||||
Alternatively, you can access the traffic flow data in the *Network Traffic* tab of the *Namespaces*, *Services*, *Routes*, *Nodes*, and *Workloads* pages which provide the filtered data of the corresponding aggregations.
|
||||
|
||||
Query Options::
|
||||
You can use *Query Options* to optimize the search results, as listed below:
|
||||
@@ -35,4 +37,4 @@ You can click *Reset defaults* to remove the existing filters, and apply the fil
|
||||
[NOTE]
|
||||
====
|
||||
To understand the rules of specifying the text value, click *Learn More*.
|
||||
====
|
||||
====
|
||||
@@ -23,7 +23,7 @@ include::modules/network-observability-enriched-flows.adoc[leveloffset=+1]
|
||||
|
||||
[role="_additional-resources"]
|
||||
.Additional resources
|
||||
* xref:../../observability/network_observability/json-flows-format-reference.adoc#network-observability-flows-format_json_reference[Network flows format reference].
|
||||
* xref:../../observability/network_observability/json-flows-format-reference.adoc#network-observability-flows-format_json_reference[Network flows format reference]
|
||||
|
||||
include::modules/network-observability-configuring-FLP-sampling.adoc[leveloffset=+1]
|
||||
|
||||
|
||||
@@ -20,11 +20,12 @@ include::modules/network-observability-without-loki.adoc[leveloffset=+1]
|
||||
|
||||
[role="_additional-resources"]
|
||||
.Additional resources
|
||||
* xref:../../observability/network_observability/configuring-operator.adoc#network-observability-enriched-flows_network_observability[Export enriched network flow data].
|
||||
* xref:../../observability/network_observability/configuring-operator.adoc#network-observability-enriched-flows_network_observability[Export enriched network flow data]
|
||||
|
||||
include::modules/network-observability-loki-install.adoc[leveloffset=+1]
|
||||
|
||||
include::modules/network-observability-loki-secret.adoc[leveloffset=+2]
|
||||
|
||||
[role="_additional-resources"]
|
||||
.Additional resources
|
||||
* xref:../../observability/network_observability/flowcollector-api.adoc#network-observability-flowcollector-api-specifications_network_observability[Flow Collector API Reference]
|
||||
@@ -44,6 +45,7 @@ include::modules/network-observability-lokistack-ingestion-query.adoc[leveloffse
|
||||
include::modules/network-observability-operator-install.adoc[leveloffset=+1]
|
||||
|
||||
include::modules/network-observability-multitenancy.adoc[leveloffset=+1]
|
||||
|
||||
[role="_additional-resources"]
|
||||
[id="additional-resources_configuring-flow-collector-considerations"]
|
||||
== Important Flow Collector configuration considerations
|
||||
@@ -58,8 +60,6 @@ Once you create the `FlowCollector` instance, you can reconfigure it, but the po
|
||||
|
||||
[role="_additional-resources"]
|
||||
.Additional resources
|
||||
For more general information about Flow Collector specifications and the Network Observability Operator architecture and resource use, see the following resources:
|
||||
|
||||
* xref:../../observability/network_observability/flowcollector-api.adoc#network-observability-flowcollector-api-specifications_network_observability[Flow Collector API Reference]
|
||||
* xref:../../observability/network_observability/configuring-operator.adoc#network-observability-flowcollector-view_network_observability[Flow Collector sample resource]
|
||||
* xref:../../observability/network_observability/configuring-operator.adoc#network-observability-resources-table_network_observability[Resource considerations]
|
||||
@@ -67,13 +67,15 @@ For more general information about Flow Collector specifications and the Network
|
||||
* xref:../../observability/network_observability/understanding-network-observability-operator.adoc#network-observability-architecture_nw-network-observability-operator[Network observability architecture]
|
||||
|
||||
include::modules/network-observability-updating-migrating.adoc[leveloffset=+2]
|
||||
|
||||
[role="_additional-resources"]
|
||||
.Additional resources
|
||||
* xref:../../operators/operator-reference.adoc#cluster-kube-storage-version-migrator-operator_operator-reference[Kubernetes Storage Version Migrator Operator]
|
||||
|
||||
include::modules/network-observability-kafka-option.adoc[leveloffset=+1]
|
||||
|
||||
[role="_additional-resources"]
|
||||
.Additional resources
|
||||
xref:../../observability/network_observability/configuring-operator.adoc#network-observability-flowcollector-kafka-config_network_observability[Configuring the FlowCollector resource with Kafka].
|
||||
* xref:../../observability/network_observability/configuring-operator.adoc#network-observability-flowcollector-kafka-config_network_observability[Configuring the FlowCollector resource with Kafka]
|
||||
|
||||
include::modules/network-observability-operator-uninstall.adoc[leveloffset=+1]
|
||||
|
||||
@@ -32,5 +32,5 @@ include::modules/network-observability-tcp-flag-syn-flood.adoc[leveloffset=+1]
|
||||
[role="_additional-resources"]
|
||||
.Additional resources
|
||||
* xref:../../observability/network_observability/observing-network-traffic.adoc#network-observability-filtering-ebpf-rule_nw-observe-network-traffic[Filtering eBPF flow data using a global rule]
|
||||
* xref:../../observability/monitoring/managing-alerts/managing-alerts-as-a-developer.adoc#creating-alerting-rules-for-user-defined-projects_managing-alerts-as-a-developer[Creating alerting rules for user-defined projects].
|
||||
* xref:../../observability/monitoring/managing-alerts/managing-alerts-as-a-developer.adoc#creating-alerting-rules-for-user-defined-projects_managing-alerts-as-a-developer[Creating alerting rules for user-defined projects]
|
||||
* xref:../../support/troubleshooting/investigating-monitoring-issues.adoc#determining-why-prometheus-is-consuming-disk-space_investigating-monitoring-issues[Troubleshooting high cardinality metrics- Determining why Prometheus is consuming a lot of disk space]
|
||||
|
||||
@@ -15,4 +15,4 @@ include::modules/network-observability-create-network-policy.adoc[leveloffset=+1
|
||||
|
||||
[role="_additional-resources"]
|
||||
.Additional resources
|
||||
xref:../../networking/network_policy/creating-network-policy.adoc#nw-networkpolicy-object_creating-network-policy[Creating a network policy using the CLI]
|
||||
* xref:../../networking/network_policy/creating-network-policy.adoc#nw-networkpolicy-create-cli_creating-network-policy[Creating a network policy using the CLI]
|
||||
|
||||
@@ -23,4 +23,4 @@ include::modules/network-observability-ebpf-agent-alert.adoc[leveloffset=+1]
|
||||
|
||||
[role="_additional-resources"]
|
||||
.Additional resources
|
||||
* For more information about creating alerts that you can see on the dashboard, see xref:../../observability/monitoring/managing-alerts/managing-alerts-as-a-developer.adoc#creating-alerting-rules-for-user-defined-projects_managing-alerts-as-a-developer[Creating alerting rules for user-defined projects].
|
||||
* xref:../../observability/monitoring/managing-alerts/managing-alerts-as-a-developer.adoc#creating-alerting-rules-for-user-defined-projects_managing-alerts-as-a-developer[Creating alerting rules for user-defined projects]
|
||||
@@ -598,7 +598,7 @@ You can now export eBPF-enriched network flows to the IPFIX collector. For more
|
||||
|
||||
[id="network-observability-packet-drop-1.4"]
|
||||
==== Packet drops
|
||||
In the 1.4 release of the Network Observability Operator, eBPF tracepoint hooks are used to enable packet drop tracking. You can now detect and analyze the cause for packet drops and make decisions to optimize network performance. In {product-title} 4.14 and later, both host drops and OVS drops are detected. In {product-title} 4.13, only host drops are detected. For more information, see xref:../../observability/network_observability/observing-network-traffic#network-observability-pktdrop-overview_nw-observe-network-traffic[Configuring packet drop tracking] and xref:../../observability/network_observability/observing-network-traffic#network-observability-packet-drops_nw-observe-network-traffic[Working with packet drops].
|
||||
In the 1.4 release of the Network Observability Operator, eBPF tracepoint hooks are used to enable packet drop tracking. You can now detect and analyze the cause for packet drops and make decisions to optimize network performance. In {product-title} 4.14 and later, both host drops and OVS drops are detected. In {product-title} 4.13, only host drops are detected. For more information, see xref:../../observability/network_observability/observing-network-traffic.adoc#network-observability-pktdrop-overview_nw-observe-network-traffic[Configuring packet drop tracking] and xref:../../observability/network_observability/observing-network-traffic.adoc#network-observability-packet-drops_nw-observe-network-traffic[Working with packet drops].
|
||||
|
||||
==== s390x architecture support
|
||||
Network Observability Operator can now run on `s390x` architecture. Previously it ran on `amd64`, `ppc64le`, or `arm64`.
|
||||
|
||||
@@ -16,5 +16,5 @@ include::modules/network-observability-nodes-taints-tolerations.adoc[leveloffset
|
||||
[role="_additional-resources"]
|
||||
.Additional resources
|
||||
* xref:../../nodes/scheduling/nodes-scheduler-taints-tolerations.adoc#nodes-scheduler-taints-tolerations-about_nodes-scheduler-taints-tolerations[Understanding taints and tolerations]
|
||||
* link:https://kubernetes.io/docs/concepts/scheduling-eviction/assign-pod-node/[Assign Pods to Nodes] (Kubernetes documentation)
|
||||
* link:https://kubernetes.io/docs/concepts/scheduling-eviction/pod-priority-preemption/#priorityclass[Pod Priority and Preemption] (Kubernetes documentation)
|
||||
* link:https://kubernetes.io/docs/concepts/scheduling-eviction/assign-pod-node/[Assign Pods to Nodes (Kubernetes documentation)]
|
||||
* link:https://kubernetes.io/docs/concepts/scheduling-eviction/pod-priority-preemption/#priorityclass[Pod Priority and Preemption (Kubernetes documentation)]
|
||||
@@ -81,8 +81,6 @@ include::modules/network-observability-configuring-options-topology.adoc[levelof
|
||||
//Quick filters
|
||||
include::modules/network-observability-quickfilter.adoc[leveloffset=+1]
|
||||
|
||||
Alternatively, you can access the traffic flow data in the *Network Traffic* tab of the *Namespaces*, *Services*, *Routes*, *Nodes*, and *Workloads* pages which provide the filtered data of the corresponding aggregations.
|
||||
|
||||
[role="_additional-resources"]
|
||||
.Additional resources
|
||||
* xref:../../observability/network_observability/configuring-operator.adoc#network-observability-config-quick-filters_network_observability[Configuring Quick Filters]
|
||||
|
||||
Reference in New Issue
Block a user