Given RHQ doesn't yet support dynamic resource plugin metadata (i.e. at runtime decide
you want to measure a new metric), there is I believe a need to support an automated
tool-chain to enable people to get closer to having this capability, while still using the
normal build-time resource plugin metadata. Does the following workflow make sense to
support this for monitoring arbitrary mbean values? Please flag any errors/omissions
1) Start off with a .txt file containing mbean names and attribute values to be monitored
2) Generate an rhq-plugin.xml from the .txt file in 1). This would extend the jmx plugin,
and for basic monitoring require no java code in the plugin
3) Package the rhq-plugin.xml from 2) into a plugin .jar file
4) Deploy the plugin .jar from 3) into an RHQ server
5) Tell the agents to go refresh their plugins
6) Agents should now be collecting all the metrics mentioned in 1)
In terms of automation I think all steps besides 4) should be feasible right now?
Regarding 4) I'm not seeing this in the remote api. Any major reason it couldn't
be added?
Cheers
Charles