I want to use this thread to begin discussion of the issues around how to associate configurable properties with monitorable properties (also I think referred to as runtime properties in previous discussions) e.g. the number of connections from a pool which are currently in use. Right now we have the concept of a ManagedComponent which supports being listed, updated, removed, created and its configurable properties queried. This component represents a user/administrator oriented feature of the app server, for example a Datasource. Its not unreasonable that such components could have monitorable attributes just as they have configurable properties, e.g. An administrator wants to know how many connections this datasource has open to the DB. Given this, some questions arise: 1) If there is a separate object, (call it a MonitoredComponent just to differentiate it) to hold these monitorable attributes then what will be the association between this new object and a ManagedComponent . How will you be able to find the one from the other. 2) Which of the two concepts will be authoritative for determining what is actually deployed to the server? Should one ask for a list of ManagedComponents or a list of MonitoredComponents in order to know how many DataSource's are available? If there is always a one to one mapping then I guess it doesn't matter. 3) Where will these MonitoredComponents be obtained from? Registered in an mbeanserver? Retrieved from some monitoring equivalent of the ProfileService? Before we start trying to answer these questions, lets see if they first make sense and if there are other more fundamental questions which need to be answered. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4012825#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...