Bug 1789023

Summary:	Convert KubeAPILatencyHigh to use anomaly detection
Product:	OpenShift Container Platform	Reporter:	Pawel Krupa <pkrupa>
Component:	Monitoring	Assignee:	Pawel Krupa <pkrupa>
Status:	CLOSED ERRATA	QA Contact:	Junqi Zhao <juzhao>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	4.1.z	CC:	alegrand, anpicker, erooth, juzhao, kakkoyun, lcosic, mloibl, pkrupa, scuppett, surbania
Target Milestone:	---
Target Release:	4.3.z
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	1789016	Environment:
Last Closed:	2020-03-10 23:52:55 UTC	Type:	---
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:	1789016
Bug Blocks:

Description Pawel Krupa 2020-01-08 15:26:46 UTC

+++ This bug was initially created as a clone of Bug #1789016 +++

A solution to https://bugzilla.redhat.com/show_bug.cgi?id=1743911

Description of problem:
KubeAPILatencyHigh alert can be triggered when there is a long-running, resource-intensive job. A solution would be to apply https://prometheus.io/blog/2015/06/18/practical-anomaly-detection/

Version-Release number of selected component (if applicable):


How reproducible:
The resolution of the alert is very consistent and I can show data from specific clusters where resolution occurs within 10 minutes of the alert triggering.

Steps to Reproduce:
1. Unknown
2.
3.

Actual results:


Expected results:


Additional info:

Comment 5 errata-xmlrpc 2020-03-10 23:52:55 UTC

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:0676