From 8a2d2da1d3407de7db9c07b1a45adc799ad13aba Mon Sep 17 00:00:00 2001
From: vathakur <vathakur@redhat.com>
Date: Wed, 2 Apr 2025 22:36:16 +0530
Subject: [PATCH] Pushing_changes_for_4.14

---
 modules/virt-querying-metrics.adoc | 17 +++++++++--------
 1 file changed, 9 insertions(+), 8 deletions(-)

diff --git a/modules/virt-querying-metrics.adoc b/modules/virt-querying-metrics.adoc
index 7f3d38114a23..a83fef4341ae 100644
--- a/modules/virt-querying-metrics.adoc
+++ b/modules/virt-querying-metrics.adoc
@@ -20,8 +20,9 @@ ifndef::openshift-rosa,openshift-dedicated[]
 
 The following query can identify virtual machines that are waiting for Input/Output (I/O):
 
-`kubevirt_vmi_vcpu_wait_seconds`::
-Returns the wait time (in seconds) for a virtual machine's vCPU. Type: Counter.
+`kubevirt_vmi_vcpu_wait_seconds_total`::
+Returns the wait time (in seconds) on I/O for vCPUs of a virtual machine. Type: Counter.
+
 
 A value above '0' means that the vCPU wants to run, but the host scheduler cannot run it yet. This inability to run indicates that there is an issue with I/O.
 
@@ -33,7 +34,7 @@ To query the vCPU metric, the `schedstats=enable` kernel argument must first be
 .Example vCPU wait time query
 [source,promql]
 ----
-topk(3, sum by (name, namespace) (rate(kubevirt_vmi_vcpu_wait_seconds[6m]))) > 0 <1>
+topk(3, sum by (name, namespace) (rate(kubevirt_vmi_vcpu_wait_seconds_total[6m]))) > 0 <1>
 ----
 <1> This query returns the top 3 VMs waiting for I/O at every given moment over a six-minute time period.
 endif::openshift-rosa,openshift-dedicated[]
@@ -80,7 +81,7 @@ topk(3, sum by (name, namespace) (rate(kubevirt_vmi_storage_read_traffic_bytes_t
 [id="virt-storage-snapshot-data_{context}"]
 === Storage snapshot data
 
-`kubevirt_vmsnapshot_disks_restored_from_source_total`::
+`kubevirt_vmsnapshot_disks_restored_from_source`::
 Returns the total number of virtual machine disks restored from the source virtual machine. Type: Gauge.
 
 `kubevirt_vmsnapshot_disks_restored_from_source_bytes`::
@@ -89,7 +90,7 @@ Returns the amount of space in bytes restored from the source virtual machine. T
 .Examples of storage snapshot data queries
 [source,promql]
 ----
-kubevirt_vmsnapshot_disks_restored_from_source_total{vm_name="simple-vm", vm_namespace="default"} <1>
+kubevirt_vmsnapshot_disks_restored_from_source{vm_name="simple-vm", vm_namespace="default"} <1>
 ----
 <1> This query returns the total number of virtual machine disks restored from the source virtual machine.
 
@@ -122,16 +123,16 @@ topk(3, sum by (name, namespace) (rate(kubevirt_vmi_storage_iops_read_total[6m])
 
 The following queries can identify which swap-enabled guests are performing the most memory swapping:
 
-`kubevirt_vmi_memory_swap_in_traffic_bytes_total`::
+`kubevirt_vmi_memory_swap_in_traffic_bytes`::
 Returns the total amount (in bytes) of memory the virtual guest is swapping in. Type: Gauge.
 
-`kubevirt_vmi_memory_swap_out_traffic_bytes_total`::
+`kubevirt_vmi_memory_swap_out_traffic_bytes`::
 Returns the total amount (in bytes) of memory the virtual guest is swapping out. Type: Gauge.
 
 .Example memory swapping query
 [source,promql]
 ----
-topk(3, sum by (name, namespace) (rate(kubevirt_vmi_memory_swap_in_traffic_bytes_total[6m])) + sum by (name, namespace) (rate(kubevirt_vmi_memory_swap_out_traffic_bytes_total[6m]))) > 0 <1>
+topk(3, sum by (name, namespace) (rate(kubevirt_vmi_memory_swap_in_traffic_bytes[6m])) + sum by (name, namespace) (rate(kubevirt_vmi_memory_swap_out_traffic_bytes[6m]))) > 0 <1>
 ----
 <1> This query returns the top 3 VMs where the guest is performing the most memory swapping at every given moment over a six-minute time period.