Hi I am not sure, whether the HealthCheck services should care about JMX at all... Otherwise you could argue the next management API around (I am sure there is something besides JMX) would want to have first class support in HealthCheck services, too. And so forth.
Whether a HealthCheck service is exposed in JMX or not, is something to be done by the HealthCheck controller, I think. Regards Felix Am 14.08.2013 um 10:20 schrieb Bertrand Delacretaz: > Hi Carsten, > > On Tue, Aug 13, 2013 at 6:13 PM, Carsten Ziegeler <[email protected]> > wrote: >> Yes, I'm not 100% sure about this - I was just wondering about how to >> disable a health check and had the idea instead of disabling the check in >> any way, simply not making it available via JMX.... > > Thinking about it there is a use case for this: I have implemented a > CompositeHealthCheck which executes other HealthChecks based on their > tags. It might make sense, when using this, to expose only the > composite as an MBean, and not the "atomic" checks. > > The simplest is to not create make the MBean if the MBean name > property is empty, WDYT? > > -Bertrand
