From e19e733941a267f6d62f2e4315b2ef2f0afa0e38 Mon Sep 17 00:00:00 2001 From: Joel Takvorian Date: Tue, 7 May 2024 15:50:32 +0200 Subject: [PATCH] update bundle --- docs/FlowMetric.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/FlowMetric.md b/docs/FlowMetric.md index 9f5c2e9d0..f3060dac1 100644 --- a/docs/FlowMetric.md +++ b/docs/FlowMetric.md @@ -148,7 +148,7 @@ When set to `Egress`, it is equivalent to adding the regex filter on `FlowDirect `filters` is a list of fields and values used to restrict which flows are taken into account. Oftentimes, these filters must be used to eliminate duplicates: `Duplicate != "true"` and `FlowDirection = "0"`. -Refer to the documentation for the list of available fields: https://docs.openshift.com/container-platform/latest/networking/network_observability/json-flows-format-reference.html.
+Refer to the documentation for the list of available fields: https://docs.openshift.com/container-platform/latest/observability/network_observability/json-flows-format-reference.html.
false @@ -160,7 +160,7 @@ From choosing labels results the level of granularity of this metric, as well as It must be done carefully as it impacts the metric cardinality (cf https://rhobs-handbook.netlify.app/products/openshiftmonitoring/telemetry.md/#what-is-the-cardinality-of-a-metric). In general, avoid setting very high cardinality labels such as IP or MAC addresses. "SrcK8S_OwnerName" or "DstK8S_OwnerName" should be preferred over "SrcK8S_Name" or "DstK8S_Name" as much as possible. -Refer to the documentation for the list of available fields: https://docs.openshift.com/container-platform/latest/network_observability/json-flows-format-reference.html.
+Refer to the documentation for the list of available fields: https://docs.openshift.com/container-platform/latest/observability/network_observability/json-flows-format-reference.html.
false @@ -169,7 +169,7 @@ Refer to the documentation for the list of available fields: https://docs.opensh `valueField` is the flow field that must be used as a value for this metric. This field must hold numeric values. Leave empty to count flows rather than a specific value per flow. -Refer to the documentation for the list of available fields: https://docs.openshift.com/container-platform/latest/networking/network_observability/json-flows-format-reference.html.
+Refer to the documentation for the list of available fields: https://docs.openshift.com/container-platform/latest/observability/network_observability/json-flows-format-reference.html.
false