Bug 1768599 - API success rate reporting 0% in console dashboard
Summary: API success rate reporting 0% in console dashboard
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Management Console
Version: 4.3.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: 4.3.0
Assignee: Rastislav Wagner
QA Contact: Yadan Pei
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-11-04 19:21 UTC by Samuel Padgett
Modified: 2020-01-23 11:10 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Version: 4.3.0-0.ci-2019-11-04-125204 Cluster ID: 76dd3e00-7385-4851-8d41-7b74ed2800ab
Last Closed: 2020-01-23 11:10:40 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
0% API success rate on dashboard (83.87 KB, image/png)
2019-11-04 19:21 UTC, Samuel Padgett 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Github openshift console pull 3313 0 'None' closed Bug 1768599: Use 0 as default value for no 5xx requests 2020-10-09 14:54:49 UTC
Red Hat Product Errata RHBA-2020:0062 0 None None None 2020-01-23 11:10:51 UTC

Description Samuel Padgett 2019-11-04 19:21:17 UTC 
Created attachment 1632716 [details]
0% API success rate on dashboard

See screenshot.
Comment 1 Rastislav Wagner 2019-11-05 09:46:07 UTC 
I cannot reproduce this on any cluster I have available. Can you share more info ? We use this query (1 - sum(rate(apiserver_request_count{code=~"5.."}[5m])) / sum(rate(apiserver_request_count[5m]))) * 100 ..does it actually return something else than 0 on your cluster ?
Comment 2 Samuel Padgett 2019-11-05 13:40:05 UTC 
I believe this happens *immediately* after you stand up a cluster when there is no data yet.
Comment 5 Yanping Zhang 2019-11-13 03:49:50 UTC 
payload: 4.3.0-0.nightly-2019-11-13-004353
After cluster is set up ,check on dashboard page, the API request success rate is 100%.
The bug is fix.
Comment 7 errata-xmlrpc 2020-01-23 11:10:40 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:0062
Note You need to log in before you can comment on or make changes to this bug.