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-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')})