fix issues

Author: jotak

content/posts/2023-12-05-acm.md

@@ -145,13 +145,13 @@ data:
 
     # Namespaces / cluster ingress|egress
     - record: namespace:netobserv_workload_egress_bytes_total:src:unknown_dst:rate5m
-      expr: sum(label_replace(rate(netobserv_workload_egress_bytes_total{DstK8S_OwnerType=\"\"}[5m]),\"namespace\",\"$1\",\"SrcK8S_Namespace\",\"(.*)\")) by (namespace)
+      expr: sum(label_replace(rate(netobserv_workload_egress_bytes_total{ DstK8S_OwnerType=\"\"}[5m]),\"namespace\",\"$1\",\"SrcK8S_Namespace\",\"(.*)\")) by (namespace)
     - record: namespace:netobserv_workload_ingress_bytes_total:dst:unknown_src:rate5m
-      expr: sum(label_replace(rate(netobserv_workload_ingress_bytes_total{SrcK8S_OwnerType=\"\"}[5m]),\"namespace\",\"$1\",\"DstK8S_Namespace\",\"(.*)\")) by (namespace)
+      expr: sum(label_replace(rate(netobserv_workload_ingress_bytes_total{ SrcK8S_OwnerType=\"\"}[5m]),\"namespace\",\"$1\",\"DstK8S_Namespace\",\"(.*)\")) by (namespace)
     - record: namespace:netobserv_workload_egress_packets_total:src:unknown_dst:rate5m
-      expr: sum(label_replace(rate(netobserv_workload_egress_packets_total{DstK8S_OwnerType=\"\"}[5m]),\"namespace\",\"$1\",\"SrcK8S_Namespace\",\"(.*)\")) by (namespace)
+      expr: sum(label_replace(rate(netobserv_workload_egress_packets_total{ DstK8S_OwnerType=\"\"}[5m]),\"namespace\",\"$1\",\"SrcK8S_Namespace\",\"(.*)\")) by (namespace)
     - record: namespace:netobserv_workload_ingress_packets_total:dst:unknown_src:rate5m
-      expr: sum(label_replace(rate(netobserv_workload_ingress_packets_total{SrcK8S_OwnerType=\"\"}[5m]),\"namespace\",\"$1\",\"DstK8S_Namespace\",\"(.*)\")) by (namespace)
+      expr: sum(label_replace(rate(netobserv_workload_ingress_packets_total{ SrcK8S_OwnerType=\"\"}[5m]),\"namespace\",\"$1\",\"DstK8S_Namespace\",\"(.*)\")) by (namespace)
 
     # Workloads
     - record: workload:netobserv_workload_egress_bytes_total:src:rate5m
@@ -251,9 +251,9 @@ We would end up with these two new rules:
 
 ```yaml
     - record: workload:netobserv_workload_egress_bytes_total:src:unknown_dst:rate5m
-      expr: sum(label_replace(label_replace(label_replace(rate(netobserv_workload_egress_bytes_total{DstK8S_OwnerType=\"\"}[5m]),\"namespace\",\"$1\",\"SrcK8S_Namespace\",\"(.*)\"),\"workload\",\"$1\",\"SrcK8S_OwnerName\",\"(.*)\"),\"kind\",\"$1\",\"SrcK8S_OwnerType\",\"(.*)\")) by (namespace,workload,kind)
+      expr: sum(label_replace(label_replace(label_replace(rate(netobserv_workload_egress_bytes_total{ DstK8S_OwnerType=\"\"}[5m]),\"namespace\",\"$1\",\"SrcK8S_Namespace\",\"(.*)\"),\"workload\",\"$1\",\"SrcK8S_OwnerName\",\"(.*)\"),\"kind\",\"$1\",\"SrcK8S_OwnerType\",\"(.*)\")) by (namespace,workload,kind)
     - record: workload:netobserv_workload_ingress_bytes_total:dst:unknown_src:rate5m
-      expr: sum(label_replace(label_replace(label_replace(rate(netobserv_workload_ingress_bytes_total{SrcK8S_OwnerType=\"\"}[5m]),\"namespace\",\"$1\",\"DstK8S_Namespace\",\"(.*)\"),\"workload\",\"$1\",\"DstK8S_OwnerName\",\"(.*)\"),\"kind\",\"$1\",\"DstK8S_OwnerType\",\"(.*)\")) by (namespace,workload,kind)
+      expr: sum(label_replace(label_replace(label_replace(rate(netobserv_workload_ingress_bytes_total{ SrcK8S_OwnerType=\"\"}[5m]),\"namespace\",\"$1\",\"DstK8S_Namespace\",\"(.*)\"),\"workload\",\"$1\",\"DstK8S_OwnerName\",\"(.*)\"),\"kind\",\"$1\",\"DstK8S_OwnerType\",\"(.*)\")) by (namespace,workload,kind)
 ```
 
 Be careful about escaping double-quotes, though it's not very pretty, it is necessary: else you would end up with a parsing error. Also, the `label_replace` chained calls here could be avoided as they look messy, but they make it actually easier to manipulate those metrics later on, in Grafana.

content/posts/2024-02-28-whats_new_1.5.md

@@ -176,13 +176,13 @@ labels:
 When you create this instance or make any changes to FlowMetric, the flowlogs-pipeline pods will restart automatically.  Now go to **Observe > Metrics** and enter `netobserv_ingress_external_bytes_total` (don't forget the prefix "netobserv_").  Because of the label, it separates out each destination namespace in its own graph line.  Try out the other PromQL queries below.
 
 1. Graph the number of bytes incoming on namespace "openshift-ingress".  You can replace with any namespace.
-`netobserv_ingress_external_bytes_total{DstK8S_Namespace="openshift-ingress"}`
+`netobserv_ingress_external_bytes_total{ DstK8S_Namespace="openshift-ingress"}`
 
 2. In some cases like "openshift-dns", you might get more than one graph line because it's running on multiple pods.  Use `sum` to combine them into one graph line.
-`sum(netobserv_ingress_external_bytes_total{DstK8S_Namespace="openshift-dns"})`
+`sum(netobserv_ingress_external_bytes_total{ DstK8S_Namespace="openshift-dns"})`
 
 3. Graph the average rate over a 5-minute interval.
-`sum(rate(netobserv_ingress_external_bytes_total{DstK8S_Namespace="openshift-ingress"}[5m]))`
+`sum(rate(netobserv_ingress_external_bytes_total{ DstK8S_Namespace="openshift-ingress"}[5m]))`
 
 ## Conclusion
 

content/posts/2024-04-05-agent_metrics_perf.md

@@ -51,7 +51,7 @@ The dashboard shows a stable number of flows captured per second, most of the ti
 
 ![Flows per second]({page.image('agent_metrics_perf/fps-1.png')})
 
-We may also check the `hey-ho` traffic captured by NetObserv, in bytes per second, with this `promql` query: `sum(rate(netobserv_workload_ingress_bytes_total{DstK8S_Namespace=~"gallery.*",DstK8S_OwnerType="Deployment"}[2m]))`. It is very stable at 4MBps:
+We may also check the `hey-ho` traffic captured by NetObserv, in bytes per second, with this `promql` query: `sum(rate(netobserv_workload_ingress_bytes_total{ DstK8S_Namespace=~"gallery.*",DstK8S_OwnerType="Deployment"}[2m]))`. It is very stable at 4MBps:
 
 ![Hey-ho traffic]({page.image('agent_metrics_perf/heyho-mbps-1.png')})
 
@@ -120,7 +120,7 @@ Even if there are five metrics, it shows mostly three things: the deduper cache
 
 The buffer size metrics tell us that the hashmaps are containing between 15K and 25K elements, which is a sum for every eBPF agent pods. We are interested to know if the hashmap configuration isn't over-sized. We can click the Inspect link and edit a little bit the promQL to see per-pod utilization:
 
-`netobserv_agent_buffer_size{name="hashmap-unique"}` shows per-pod maps size, or `max(netobserv_agent_buffer_size{name="hashmap-unique"})` shows the maximum map utilization across pods.
+`netobserv_agent_buffer_size{ name="hashmap-unique"}` shows per-pod maps size, or `max(netobserv_agent_buffer_size{ name="hashmap-unique"})` shows the maximum map utilization across pods.
 
 ![Per-pod size]({page.image('agent_metrics_perf/per-pod-hashmap-size.png')})
 

content/posts/2024-10-23-whats_new_1.6.md

@@ -168,7 +168,7 @@ _<div style="text-align: center">Figure 7: Not 'ip' filter</div>_
    By default, the OpenShift auto-detect mode is enabled to identify internal CIDRs as `Pods`, `Services`, `Machines` or `n/a` for not applicable.  While CIDRs can be internal or external, they are typically external to allow you to provide a custom name for them.  If you use a naming convention such as prefixing "Ext_" for all cluster-external traffic, then you can create a custom metric for this.  Here's a PromQL that displays a graph of external traffic in bytes over a 1-minute period.
 
    ```
-   sum(rate(netobserv_workload_egress_bytes_total{DstSubnetLabel=~"|Ext_.*"}[1m]))
+   sum(rate(netobserv_workload_egress_bytes_total{ DstSubnetLabel=~"|Ext_.*"}[1m]))
    ```
 
    This assumes the `workload_egress_bytes_total` metric has been included in `processor.metrics.includeList`.  See my [Network Observability 1.5 blog](https://developers.redhat.com/articles/2024/03/20/whats-new-network-observability-15) on how to do this.