Bug 1845443
Summary: | KubeApiLatency alert firing even though not all conditions are matched | |||
---|---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | Rick Rackow <rrackow> | |
Component: | Monitoring | Assignee: | Rick Rackow <rrackow> | |
Status: | CLOSED WONTFIX | QA Contact: | Junqi Zhao <juzhao> | |
Severity: | low | Docs Contact: | ||
Priority: | low | |||
Version: | 4.3.z | CC: | alegrand, anpicker, erooth, kakkoyun, lcosic, mloibl, pkrupa, surbania, wking | |
Target Milestone: | --- | |||
Target Release: | 4.3.z | |||
Hardware: | Unspecified | |||
OS: | Unspecified | |||
Whiteboard: | wip | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | ||
Doc Text: | Story Points: | --- | ||
Clone Of: | ||||
: | 1845444 (view as bug list) | Environment: | ||
Last Closed: | 2020-06-30 08:35:40 UTC | Type: | Bug | |
Regression: | --- | Mount Type: | --- | |
Documentation: | --- | CRM: | ||
Verified Versions: | Category: | --- | ||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | ||
Cloudforms Team: | --- | Target Upstream Version: | ||
Embargoed: | ||||
Bug Depends On: | 1845444 | |||
Bug Blocks: |
OCP 4.3 is leaving the full support and approaching EOL, therefore backporting to it does not seem like a viable option |
Description of problem: KubeApiLatencyHigh warning should only be firing if all conditions are met AND the latency is over 1s. However we have seen this fire with ``` The API server has an abnormal latency of 0.05685404799999992 seconds for PUT namespace ``` Version-Release number of selected component (if applicable): OpenShift Dedicated 4.3.18 How reproducible: Partially Steps to Reproduce: 1. Execute alerting rule in Prometheus to graph 2. Scroll out until you find an occurence Actual results: 0.05685404799999992 Expected results: >1 Additional info: This can as well be fixed by adjusting the message to be something more meaningful