Merge pull request #105163 from openshift-cherrypick-robot/cherry-pick-102805-to-enterprise-4.21

[enterprise-4.21] CNV- 58843: Added <shortdesc> to Monitoring sections

Author: sjhala-ccs

modules/virt-querying-metrics.adoc

@@ -80,8 +80,7 @@ topk(3, sum by (name, namespace) (rate(kubevirt_vmi_network_receive_bytes_total[
 [id="virt-promql-storage-metrics_{context}"]
 == Storage metrics
 
-[id="virt-storage-traffic_{context}"]
-=== Storage-related traffic
+You can monitor virtual machine storage traffic and identify high-traffic VMs by using Prometheus queries.
 
 The following queries can identify VMs that are writing large amounts of data:
 --
@@ -108,8 +107,7 @@ topk(3, sum by (name, namespace) (rate(kubevirt_vmi_storage_read_traffic_bytes_t
 topk(3, sum by (name, namespace) (rate(kubevirt_vmi_storage_read_times_seconds_total{name='${name}',namespace='${namespace}'${clusterFilter}}[6m]) / rate(kubevirt_vmi_storage_iops_read_total{name='${name}',namespace='${namespace}'${clusterFilter}}[6m]) > 0)) > 0
 ----
 
-[id="virt-storage-snapshot-data_{context}"]
-=== Storage snapshot data
+The following queries can track data restored from storage snapshots:
 
 `kubevirt_vmsnapshot_disks_restored_from_source`::
 Returns the total number of virtual machine disks restored from the source virtual machine. Type: Gauge.
@@ -134,8 +132,6 @@ kubevirt_vmsnapshot_disks_restored_from_source_bytes{vm_name="simple-vm", vm_nam
 ----
 
 
-[id="virt-iops_{context}"]
-=== I/O performance
 
 The following queries can determine the I/O performance of storage devices: