Bug 536401 (RHQ-754)
| Summary: | "Get current values" button should trigger a fetch of the current metrics from the agent | ||
|---|---|---|---|
| Product: | [Other] RHQ Project | Reporter: | Heiko W. Rupp <hrupp> |
| Component: | Monitoring | Assignee: | John Mazzitelli <mazz> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | unspecified | CC: | ccrouch, cwelton, jpviragine, mazz, mfoley |
| Target Milestone: | --- | Keywords: | FutureFeature |
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | All | ||
| URL: | http://jira.rhq-project.org/browse/RHQ-754 | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Enhancement | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2013-09-03 17:00:49 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | |||
| Bug Blocks: | 585306, 678340 | ||
|
Description
Heiko W. Rupp
2008-08-25 10:04:00 UTC
but, heiko, what happens if you're viewing metric data for a compatible group that just so happens to modestly span, say, 25 agents. do we really expect the server to go contact all known agents and wait until all data is available before displaying the page? also, how will this work in the HA world? each server is only going to have direct access to a subset of all known agents in the system as part of the way it natural load balances. I think it could be a compromise to only allow this for single resources and not for groups. Groups are sort of special anyway, as in normal operation no two metrics from different resources will arrive at the same time. This "trigger a fetch" is something that comes up every now and then from customers and users - the current behavior is erratic. The 'fake' solution would be to rename the button to 'redraw'. HA makes things indeed somewhat more difficult. How does updating the metric schedule on server 1 work when the agent is on server 2? In this case, there needs to be some communication between servers too, as we can't wait until the agent perhaps connects to server 1 for this. This issue will cause confusion for SOA-P users - the legacy ESB mgmt console does allow for async collections of stats: https://jira.jboss.org/jira/browse/SOA-929 So - can we get it fixed? ;-) once this is implemented, the label of the button should also change to say "Get Live Values" as opposed to "Get Current Values". This bug was previously known as http://jira.rhq-project.org/browse/RHQ-754 Mass move to component = Monitoring i will take a look to see what can be done. I have gwt-ified the Measurement>Tables subtab. And there is now a "Get Live Data" button on it. You select one or more metrics in the table and you click the button to pop up a dialog that contains a table of the metrics with their live data as retrieved from the agent. verified RHQ 4.0 community release, as follows: on Monitoring, Tables sub-tab ... there is the both Refresh (to reload the page), and Get Live Data ... to get live data from the agent. Both seem to work. When I click Get Live Data on a volatile resource (User Load on the RHQ Agent) I see the numbers changing each time. Bulk closing of old issues that are in VERIFIED state. |