-
Bug
-
Resolution: Done
-
Undefined
-
None
-
0.42
-
False
-
False
-
CNV-8094 - CNV Observability
-
---
-
---
-
-
CNV I/U Operators Sprint 250, CNV I/U Operators Sprint 251, CNV I/U Operators Sprint 252
-
No
Description of problem:
Deprecate the KubeVirtComponentExceedsRequestedCPU and KubeVirtComponentExceedsRequestedMemory alerts Update the deprecated alerts runbooks and suggest to silence the alerts. CNV-38320 will handle adding a metric to be able to track this issue without creating noise to the customer.
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1. 2. 3.
Actual results:
Customer get alerts that he can't fix
Expected results:
Customer will not get alerts about this
Additional info:
Git Pull Request: https://github.com/kubevirt/monitoring/pull/222 closed
Git Pull Request: https://github.com/kubevirt/kubevirt/pull/11404 closed
Git Pull Request: https://github.com/kubevirt/kubevirt/pull/11445 closed
Git Pull Request: https://github.com/kubevirt/kubevirt/pull/11444 closed
Git Pull Request: https://github.com/kubevirt/kubevirt/pull/11443 closed
Git Pull Request: https://github.com/openshift/runbooks/pull/172 closed
- is cloned by
-
CNV-39980 Doc: Deprecate KubeVirtComponentExceedsRequestedCPU and KubeVirtComponentExceedsRequestedMemory alerts
- Closed
-
CNV-38320 Collect a metric to Telemetry if memory exceeds requested memory
- Closed
- is related to
-
CNV-37899 virt-controller memeory usage can go as high as 2G over the requested amount
- Closed
- relates to
-
CNV-28429 Missing option in HCO to set resources requests for cpu and memory for different components
- Closed
-
CNV-30274 [2217243] virt-handler memory and cpu usage are hardcoded and set too low for large scale
- Closed
-
CNV-30426 KubeVirtComponentExceedsRequestedMemory alerts on virt-handler
- Closed
- links to