Bug 1845443 - KubeApiLatency alert firing even though not all conditions are matched
Summary: KubeApiLatency alert firing even though not all conditions are matched
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Monitoring
Version: 4.3.z
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: ---
: 4.3.z
Assignee: Rick Rackow
QA Contact: Junqi Zhao
URL:
Whiteboard: wip
Depends On: 1845444
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-06-09 09:13 UTC by Rick Rackow
Modified: 2020-06-30 08:35 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1845444 (view as bug list)
Environment:
Last Closed: 2020-06-30 08:35:40 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Rick Rackow 2020-06-09 09:13:46 UTC 
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
Comment 2 Rick Rackow 2020-06-30 08:35:40 UTC 
OCP 4.3 is leaving the full support and approaching EOL, therefore backporting to it does not seem like a viable option
Note You need to log in before you can comment on or make changes to this bug.