Bug 1028450 - cluster alerts count long load time
cluster alerts count long load time
Status: NEW
Product: RHQ Project
Classification: Other
Component: Core UI (Show other bugs)
x86_64 Linux
unspecified Severity medium (vote)
: ---
: ---
Assigned To: RHQ Project Maintainer
Mike Foley
Depends On:
  Show dependency treegraph
Reported: 2013-11-08 08:25 EST by Armine Hovsepyan
Modified: 2015-09-02 20:04 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
clusterAlertsCount (130.20 KB, image/png)
2013-11-08 08:25 EST, Armine Hovsepyan
no flags Details

  None (edit)
Description Armine Hovsepyan 2013-11-08 08:25:45 EST
Created attachment 821614 [details]

Description of problem:
cluster alerts count long load time

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

How reproducible:

Steps to Reproduce:
1. Navigate to Administration -> Storage nodes (when there are cluster alerts)
2. Navigate to Cluster Alerts

Actual results:
After step1 and 2 very frequently alert count is not visible 
after step 2 count is being loaded later than alert

Expected results:
cluster alerts count is displayed when storage nodes and/or cluster alerts pages are loaded

Additional info:
screen-shot attached
Comment 1 Heiko W. Rupp 2013-11-08 08:34:40 EST
Could you specify what is missing, as I don't see it from the screen shot. Is it the (0/1) you mean? 
I think it would be valid if there is a load indicator to lazy load this, so that page load/display can happen even if the data is still computed.
Comment 2 Armine Hovsepyan 2013-11-08 08:48:36 EST
Next to Cluster Alerts tab there should be the count of not acknowledged alerts. The real count is 1, while the value missing there means 0.

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