+++ This bug was initially created as a clone of Bug #1845444 +++ +++ This bug was initially created as a clone of Bug #1845443 +++ 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
tested with 4.5.0-0.nightly-2020-07-14-022827, KubeAPILatencyHigh alert details see below, and there is not such alert in the cluster ************************************************* - alert: KubeAPILatencyHigh annotations: message: The API server has an abnormal latency of {{ $value }} seconds for {{ $labels.verb }} {{ $labels.resource }}. expr: | cluster_quantile:apiserver_request_duration_seconds:histogram_quantile{job="apiserver",quantile="0.99"} > 1 and on (verb,resource) ( cluster:apiserver_request_duration_seconds:mean5m{job="apiserver"} > on (verb) group_left() ( avg by (verb) (cluster:apiserver_request_duration_seconds:mean5m{job="apiserver"} >= 0) + 2*stddev by (verb) (cluster:apiserver_request_duration_seconds:mean5m{job="apiserver"} >= 0) ) ) > on (verb) group_left() 1.2 * avg by (verb) (cluster:apiserver_request_duration_seconds:mean5m{job="apiserver"} >= 0) for: 5m labels: severity: warning
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2020:2909