-
1. Re: Relating configuration and monitoring
starksm64 Feb 8, 2007 1:40 AM (in response to ccrouch)I would just view this as a quality/annotation of the existing ManagedProperty notion.
A configuration type of property has:
- Realtime, RequriesRestart in terms when it can be applied
- The edit information, min, max, allowed values, ...
A statistic type of property has:
- type, expected range?
The management interface of a component should include both configuration and statistics type properties. -
2. Re: Relating configuration and monitoring
ccrouch Feb 8, 2007 11:48 AM (in response to ccrouch)Ok, given this, would you expect the JSR77 implementation to be based off these ManagedComponent's and ManagedProperty's?
-
3. Re: Relating configuration and monitoring
starksm64 Feb 8, 2007 12:28 PM (in response to ccrouch)Yes, but I"m not sure what else might need to be updated to support this yet. I believe the existing jmx notification based stuff should map over to an aspect that exposes a ManagedDeployment and its ManagedComponents as the jsr77 mbeans.
-
4. Re: Relating configuration and monitoring
adrian.brock Feb 12, 2007 9:26 AM (in response to ccrouch)"scott.stark@jboss.org" wrote:
A statistic type of property has:
- type, expected range?
Actually, I was thinking that the ManagedObject interface would have
a seperate part of statistics. This avoids the users having to "weed"
the managed properties when displaying what the user can change.
And vice versa when displaying what can be monitored. -
5. Re: Relating configuration and monitoring
adrian.brock Feb 12, 2007 9:32 AM (in response to ccrouch)"scott.stark@jboss.org" wrote:
Yes, but I"m not sure what else might need to be updated to support this yet. I believe the existing jmx notification based stuff should map over to an aspect that exposes a ManagedDeployment and its ManagedComponents as the jsr77 mbeans.
I think we should really be doing this on the ManagedObjects?
We already have a type, so once we have the notion of scope in the ManagedObjects
it should be relatively trivial to map them to the jsr77 tree/naming convention?
I think the only issue is whether we enforce that the POJOs/MBeans should implement
the jsr77 classes, e.g. the statistics classes or whether we do some adaption in the jsr77 facade?
I'd favour the latter simply because it allows the implementation to provide
custom extra statistics and seperate the invocation/pooling/caching stats
while still being able to map them to the standard classes for jsr77.
The downside is that it is going to require some knowledge (hard wiring)
of the real implementation in the jsr77 facade to make this work. -
6. Re: Relating configuration and monitoring
starksm64 Feb 12, 2007 11:18 AM (in response to ccrouch)I agree, that the management view from the deployer should be able to define the jsr77 view. We do need to be able to override this to bootstrap it and deal with the missing info and mismatches, as well as the jmx registration/naming conventions.