Hi There is no such thing as a JMX Bean tree. Each JMX Bean has an ObjectName and the only official structuring is by the MBean's domain. The rest of name is just name-value pairs. Nothing much that you can say, Beans are structured in a tree.
The new JMX resource provider is different in that it tries to build a tree structure from the ObjectName but we should not try to do such a thing in the HC context. Rather I think, if the HC controller registers all HealthCheck services as MBeans it should use a commong domain and use some of the important service registration properties as name-value pairs of the object name. Regards Felix Am 13.08.2013 um 18:07 schrieb Bertrand Delacretaz: > On Tue, Aug 13, 2013 at 5:09 PM, Carsten Ziegeler <[email protected]> > wrote: >> right now, all HCs are registered as mbeans - I'm just wondering if we need >> an opt-in or opt-out mechanism? > > I think in general they should all be exposed, as long as they can be > organized cleanly which is possible. > > You can place MBeans in a specific place in the JMX tree, if you set > hc.mean.name = foo/thisbean for example, it will appear under > org.apache.sling.healthcheck/foo/thisbean whereas by default MBeans go > under org.apache.sling.healthcheck/HealthCheck. So you can already > create subsets of interesting HC MBeans, without having too many > options to care about. > > -Bertrand
