Skip to content

Commit 94c2e94

Browse files
authored
Merge pull request #96742 from Vaishali-gif-rh/CNV#61371
CNV - 61371-- Added AAQ metrics_revised PR
2 parents 5b17e6a + e3b4d77 commit 94c2e94

File tree

1 file changed

+14
-3
lines changed

1 file changed

+14
-3
lines changed

modules/virt-querying-metrics.adoc

Lines changed: 14 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -22,8 +22,7 @@ ifndef::openshift-rosa,openshift-dedicated[]
2222
The following query can identify virtual machines that are waiting for Input/Output (I/O):
2323

2424
`kubevirt_vmi_vcpu_wait_seconds_total`::
25-
Returns the wait time (in seconds) on I/O for vCPUs of a virtual machine. Type: Counter.
26-
25+
Returns the wait time (in seconds) on I/O for vCPUs of a virtual machine. Type: Counter.
2726

2827
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.
2928

@@ -65,18 +64,20 @@ topk(3, sum by (name, namespace) (rate(kubevirt_vmi_network_receive_bytes_total[
6564
=== Storage-related traffic
6665

6766
The following queries can identify VMs that are writing large amounts of data:
68-
67+
--
6968
`kubevirt_vmi_storage_read_traffic_bytes_total`::
7069
Returns the total amount (in bytes) of the virtual machine's storage-related traffic. Type: Counter.
7170

7271
`kubevirt_vmi_storage_write_traffic_bytes_total`::
7372
Returns the total amount of storage writes (in bytes) of the virtual machine's storage-related traffic. Type: Counter.
73+
--
7474

7575
*Example storage-related traffic query*
7676
[source,promql]
7777
----
7878
topk(3, sum by (name, namespace) (rate(kubevirt_vmi_storage_read_traffic_bytes_total[6m])) + sum by (name, namespace) (rate(kubevirt_vmi_storage_write_traffic_bytes_total[6m]))) > 0 <1>
7979
----
80+
8081
<1> This query returns the top 3 VMs performing the most storage traffic at every given moment over a six-minute time period.
8182

8283
[id="virt-storage-snapshot-data_{context}"]
@@ -134,10 +135,20 @@ Returns the total amount (in bytes) of memory the virtual guest is swapping out.
134135
[source,promql]
135136
----
136137
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>
138+
+
137139
----
138140
<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.
139141

140142
[NOTE]
141143
====
142144
Memory swapping indicates that the virtual machine is under memory pressure. Increasing the memory allocation of the virtual machine can mitigate this issue.
143145
====
146+
[id=virt-promql-AAQ-metrics_context]
147+
== Monitoring AAQ operator metrics
148+
The following metrics are exposed by the Application Aware Quota (AAQ) controller for monitoring resource quotas:
149+
150+
`kube_application_aware_resourcequota`::
151+
Returns the current quota usage and the CPU and memory limits enforced by the AAQ Operator resources. Type: Gauge.
152+
153+
`kube_application_aware_resourcequota_creation_timestamp`::
154+
Returns the time, in UNIX timestamp format, when the AAQ Operator resource is created. Type: Gauge.

0 commit comments

Comments
 (0)