Bug 1913554

Summary: Recording rule for ingress error fraction SLI is incorrect, uses irate instead of increase
Product: OpenShift Container Platform Reporter: Clayton Coleman <ccoleman>
Component: NetworkingAssignee: aos-network-edge-staff <aos-network-edge-staff>
Networking sub component: router QA Contact: Arvind iyengar <aiyengar>
Status: CLOSED ERRATA Docs Contact:
Severity: high    
Priority: unspecified CC: aiyengar, amcdermo, aos-bugs, hongli, sgreene
Version: 4.7   
Target Milestone: ---   
Target Release: 4.7.0   
Hardware: Unspecified   
OS: Unspecified   
Fixed In Version: Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-02-24 15:50:41 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Clayton Coleman 2021-01-07 05:39:16 UTC
A copy and paste error in the ingress rule for cluster:usage:workload:ingress_request_error:fraction5m and cluster:usage:openshift:ingress_request_error:fraction5m led to them being increase/irate, which yields numbers greater than 1 (which is bad for fractions).

The denominator should be increase to be consistent (instead of switching numerator to irate) in order to make the value more stable over a window.

The fraction is useless as is so needs to be fixed to track this for an SLI.

Comment 2 Arvind iyengar 2021-01-11 11:08:05 UTC
Verified in "4.7.0-0.nightly-2021-01-09-144822" which contains the merge.

Comment 5 errata-xmlrpc 2021-02-24 15:50:41 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 (Moderate: OpenShift Container Platform 4.7.0 security, bug fix, and enhancement 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.