What version of RHQ? (RHQ 4.4 introduced alot of changes to the availability scanning stuff).
After you get the initial availability scan, does it update fairly quickly thereafter? If so, could it be a startup issue? (maybe it took a very long time for your agents to start, register, download plugins, start the plugin container and begin avail scanning? If the boxes are heavily loaded, perhaps it takes a long time? I realize 30m would be extremely long (and I can't say I've ever heard of the agent taking 30m to do all that) but the question remains - does this only happen on startup of the agent? Or does it take 30m to report ANY availability change while the agent is running.
I haven't looked at the Process resource type and its resource component code in a while, look in the agent logs and see if there are any log messages regarding errors happening with that plugin. (you should run the agent in debug mode to see if that would be more verbose).
What about everything else about the agent? Is it working OK (all other resources respond quickly? All avail statuses and metrics coming in OK?)
----- Original Message -----
We’ve setup three nodes with RHEL5.3 and same hardware specifications. One for RHQ server and remaining two for RHQ agents to monitor mongoDB.
mongoDB is monitored using Process resource type with Pid File and PIQL query types. Each query type is setup on a different node. However we found that the availability scan for both agents does not respond in a decent time. In fact sometimes it takes more than 30 minutes to reflect the actual availability of mongoDB. We’re using default configuration in agent. The value for rhq.agent.plugins.availability-scan.period-secs is also default (30 seconds).
Anyone encounter this problem before?