Bug 907858 - CPU usage report may fail or is slow if agent is down
CPU usage report may fail or is slow if agent is down
Status: NEW
Product: RHQ Project
Classification: Other
Component: Core Server (Show other bugs)
4.5
Unspecified Unspecified
unspecified Severity unspecified (vote)
: ---
: ---
Assigned To: RHQ Project Maintainer
Mike Foley
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2013-02-05 07:34 EST by Heiko W. Rupp
Modified: 2013-02-05 07:34 EST (History)
1 user (show)

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


Attachments (Terms of Use)

  None (edit)
Description Heiko W. Rupp 2013-02-05 07:34:38 EST
The Reports->CPU Usage report may be very slow of even fail in the UI as it tries to get live metrics from the agents. If now one agent is not reachable, the UI shows the yellow "I waited too long, but the operation may still go on" box and a popup shows "Failure".

Clicking on "reload" does not help, as this also does not show the values last retrieved, but again tries to go out to the agents.

The get live values should perhaps try to ping the agent and if this is not available within a very short time, abort and just return the last retrieved metrical value.
Or totally switch to getting the last metrical value and then polling cpu usage and memory usage much more often than what we do today.

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