Created attachment 1952088 [details]
A Photo of the metric

Created attachment 1952088 [details]
A Photo of the metric

Description of problem:
When trying to validate the VirtApiRESTErrorsBurst critical alerts with automation, this alert is not fired and stays on pending, when the rest calls is getting little lower than 0.8 it counting again for the 5 mins so the alert can't get to the firing state withing reasonable time, it can take more than 20 mins.

How reproducible:
This is the steps:
1.Scale virt-operator to zero (Otherwise, it will revert our changes to observe the alert),
oc -n openshift-cnv scale deployment virt-operator --replicas=0
2.Run a VM
3.Backup clusterrolebinding for kubevirt-apiserver,
oc get clusterrolebinding kubevirt-apiserver -o yaml > kubevirt-apiserver-clusterrolebinding.yaml
4.Delete clusterrolebinding for virt-api:
oc delete clusterrolebinding kubevirt-apiserver
Now Wait for a while and observe the alert.
5.Recreate the clusterrolebinding: oc apply -f kubevirt-apiserver-clusterrolebinding.yaml
6.Stop the VM
7.Rescale virt-operator to its original replicas: oc -n openshift-cnv scale deployment virt-operator --replicas=2

Actual results:
VirtApiRESTErrorsBurst in Pending state

Expected results:
VirtApiRESTErrorsBurst in fire state

Additional info:
Attached a Photo of the metric