Am 26.01.2011 um 14:35 schrieb Emanuel Muckenhuber:
>
This does seem to go a bit beyond metrics - In general it's the logical
configuration view vs. the actual runtime state of a domain. Where i'm
not sure it makes much sense trying to combine them into one single view
(well let's say one which can be retrieved with recursive=true).
First from a tooling perspective i don't think you want to have the
metrics from possibly 100 servers together with the configuration (where
you rather either pick one of them). Also if we allow system property
replacement for standalone the actual runtime state is again different
I guess this is also a question of scaling.
RHQ for example may come in and request metrics every few seconds (*) while
configuration changes / updates / reads are a lot less frequent. So the load on the
DC and HCs will probably increase with the number of items processed.
So a separation between runtime state and configuration may make sense for
processing (not for metadata).
Heiko
*) Actually the user can give for each metric a different interval, so that there will be
many
single item reads
--
Reg. Adresse: Red Hat GmbH, Otto-Hahn-Strasse 20, 85609 Dornach bei München
Handelsregister: Amtsgericht München HRB 153243
Geschaeftsführer: Brendan Lane, Charlie Peters, Michael Cunningham, Charles Cachera