Description of problem: Cluster admin check Alerting page such as Watchdog (or Alerting Rule page), chart is quick enough to show. Click 'View in Metrics' will browse to Metics page and the chart is too slow to show. Version-Release number of selected component (if applicable): 4.5.0-0.nightly-2020-04-06-184201 How reproducible: Always Steps to Reproduce: 1. Cluster admin user goes to Alerting page, such as Watchdog (or from Alerting detail page goes to Alerting Rule page) 2. Check the chart, now it's quick enough to show. 3. Click 'View in Metrics' and check the chart on Metrics page Actual results: 3. Chart is too slow to show which needs at least 10 seconds. Expected results: 3. Should show the chart as same speed as in Alerting/Alerting Rule page. Additional info: Firefox 74.0
Same issue if query metrics directly from Query Browser
(In reply to Junqi Zhao from comment #1) > Same issue if query metrics directly from Query Browser same issue if query metrics from developer/cluster admin Query Browser
We will look into this in the next sprint.
I was not able to reproduce this. I checked Watchdog, as well as several others. Clicking "show in metrics" loaded the chart reasonably quick each time.
(In reply to bpeterse from comment #4) > I was not able to reproduce this. I checked Watchdog, as well as several > others. Clicking "show in metrics" loaded the chart reasonably quick each > time. what is your browser version, we used Firefox/Chrome, it takes 15 seconds to load the chart after clicking "View in Metrics", see the attached gif recorded on Google Chrome 79.0.3945.130 (Official Build) (64-bit)
Created attachment 1689507 [details] takes about 15 seconds to load chart
Created attachment 1689535 [details] reproduces on 4.5.0-0.nightly-2020-05-18-031304 with Firefox 76.0.1
This bug was introduced by the change to `useRefWidth` in https://github.com/openshift/console/pull/4841
Created attachment 1689730 [details] Verification screenshot
Chart is quickly to show now. Attached the screen recording for refer. Verified on 4.5.0-0.nightly-2020-05-19-011623
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:2409