Bug 1807139 - Alert on OOMKills on the cluster as a symptom of disruptive workloads or bugs
Summary: Alert on OOMKills on the cluster as a symptom of disruptive workloads or bugs
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Node
Version: 4.4
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: 4.5.0
Assignee: Lili Cosic
QA Contact: Sunil Choudhary
Depends On:
Blocks: 1807140
TreeView+ depends on / blocked
Reported: 2020-02-25 17:09 UTC by Clayton Coleman
Modified: 2020-08-04 18:02 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
Clone Of:
: 1807140 (view as bug list)
Last Closed: 2020-08-04 18:02:10 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Github openshift cluster-monitoring-operator pull 690 0 None closed Bug 1807139: jsonnet/rules.jsonnet: Lower threshold for MultipleContainersOOMKilled alert 2020-08-18 08:42:06 UTC
Red Hat Product Errata RHBA-2020:2409 0 None None None 2020-08-04 18:02:14 UTC

Description Clayton Coleman 2020-02-25 17:09:15 UTC
An OOMKill on a cluster can be disruptive to workloads and infrastructure both immediately and over time (if a component partially fails).  We should alert when a significant number of OOMKills have occurred.

As a starting point, we should pick a rate that we believe is likely to indicate serious problems and tune it down (to catch more issues) after we assess the impact in the field.  The alert should be at 'info' level for now in order to allow time for assessment.

Should be back ported to 4.3 where OOMKills may have caused significant production issues for a few customers.

Comment 4 Lili Cosic 2020-04-20 10:03:19 UTC
Already in the release notes, no need for extra docs.

Comment 6 errata-xmlrpc 2020-08-04 18:02:10 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 (OpenShift Container Platform 4.5 image release 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.


Note You need to log in before you can comment on or make changes to this bug.