Bug 1866020 - Operator alerts for error count and should alert for error rate
Summary: Operator alerts for error count and should alert for error rate
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Logging
Version: 4.6
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: ---
: 4.6.0
Assignee: Brett Jones
QA Contact: Anping Li
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-08-04 16:44 UTC by Brett Jones
Modified: 2020-10-27 15:10 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-10-27 15:09:34 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift cluster-logging-operator pull 646 0 None closed Bug 1866020: alert on error rate % 2021-01-05 09:02:33 UTC
Red Hat Product Errata RHBA-2020:4198 0 None None None 2020-10-27 15:10:14 UTC

Description Brett Jones 2020-08-04 16:44:05 UTC 
Description of problem:

The current alert for CLO error rate logs at an arbitrary limit of 10rps. It should be based on a percentage because message counts can increase and decrease over time where 10 errors might be a very small amount of logs. 

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

4.6

How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
Comment 5 Anping Li 2020-08-18 08:13:27 UTC 
Verified on clusterlogging.4.6.0-202008130129.p0 by making the kafka failed for 'error_class=Kafka::MessageSizeTooLarge'
Comment 7 errata-xmlrpc 2020-10-27 15:09:34 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.6.1 extras update), 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:4198
Note You need to log in before you can comment on or make changes to this bug.