Currently we are running availability scans on the agent, which is much too long for many users - even the default 60 seconds are often too long see comments on http://javablogs.com/Jump.action?id=534624 as example. What we could do is on the agent side to run availability scans much more often and only send a partial availability report to the server if a resource is found that is down, which was not down in the previous run. The regular reports with backfilling etc. would still run as is. Those fast scans have the advantage of fast detection of possibly downed servers without clobbering the network or hammering the servers.
This bug was previously known as http://jira.rhq-project.org/browse/RHQ-2483
Mass move to component= Monitoring
Triaged 5-Oct
I believe this has been addressed in the jshaughn/avail branch with the ability to schedule resource avail checks as low as every 30 seconds. http://rhq-project.org/display/RHQ/Design-Availability+Checking#Design-AvailabilityChecking-PrioritizedAvailChecking Asking Heiko if he believes the essence of this bz has been resolved.
I think the change mentioned in comment 4 does indeed what is requested here ( even if I still think that 30s minimum intervals may be too long )
This is in master.
Bulk closing of items that are on_qa and in old RHQ releases, which are out for a long time and where the issue has not been re-opened since.