[jira] [Commented] (SLING-2999) JMX Resource Provider
[ https://issues.apache.org/jira/browse/SLING-2999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13736872#comment-13736872 ] Carsten Ziegeler commented on SLING-2999: - Enhanced the implementation to create a tree based on the domain name JMX Resource Provider - Key: SLING-2999 URL: https://issues.apache.org/jira/browse/SLING-2999 Project: Sling Issue Type: New Feature Reporter: Carsten Ziegeler Assignee: Carsten Ziegeler For easier rendering of JMX mbeans within Sling, a special resource provider should make the JMX information available at */system/sling/monitoring/mbeans* (Configurable) /system/sling/monitoring/mbeans - resource type = sling:mbeans + resource sub tree with all mbeans An MBean has an object name which has * a domain * properties where type and name are very common The domain is converted into a sub path and the properties are converted to a resource name. For example: _org.apache.sling:name=test,type=hello_ creates a resource _org/apache/sling/name=test,type=hello_. The name can be obtained by calling _ObjectName.getCanonicalKeyPropertyListString()_. The result might need escaping (for the values and the = character) in order to create valid resource names. Each MBean resource has at least: ||Property name ||Description| |sling:resourceType|object name of the MBean| |sling:resourceSuperType| sling:mbean| |mbean:description|The description of the MBean (optional)| |mbean:className|MBean class name| |mbean:objectName|MBean object name| |mbean properties|separate property for each property of the object name| And a child resource named _mbean:attributes_ if the MBean has attributes. For each attribute a child resource of _mbean:attributes_ is created where the name of the resource is the name of the attribute and: ||Property name ||Description| |sling:resourceType|Type of the attribute| |sling:resourceSuperType| sling:mbeanattribute| |mbean:description|The description of the attribute (optional)| |mbean:value|String representation of the value or a string array for multi values| -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (SLING-2999) JMX Resource Provider
[
https://issues.apache.org/jira/browse/SLING-2999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13736967#comment-13736967
]
Carsten Ziegeler commented on SLING-2999:
-
Rev 1513172 : I've changed the path creation to
* {Domain}/{type property}/{name property}{all other props}
A good object name should have a type property, and maybe a name property but
no others - therefore I think this path resolution makes it much easier to get
a resource based on the object name
JMX Resource Provider
-
Key: SLING-2999
URL: https://issues.apache.org/jira/browse/SLING-2999
Project: Sling
Issue Type: New Feature
Reporter: Carsten Ziegeler
Assignee: Carsten Ziegeler
For easier rendering of JMX mbeans within Sling, a special resource provider
should make the JMX information available at
*/system/sling/monitoring/mbeans* (Configurable)
/system/sling/monitoring/mbeans - resource type = sling:mbeans
+ resource sub tree with all mbeans
An MBean has an object name which has
* a domain
* properties where type and name are very common
The domain is converted into a sub path and the properties are converted to a
resource name. For example: _org.apache.sling:name=test,type=hello_ creates a
resource _org/apache/sling/name=test,type=hello_. The name can be obtained by
calling _ObjectName.getCanonicalKeyPropertyListString()_. The result might
need escaping (for the values and the = character) in order to create valid
resource names.
Each MBean resource has at least:
||Property name ||Description|
|sling:resourceType|object name of the MBean|
|sling:resourceSuperType| sling:mbean|
|mbean:description|The description of the MBean (optional)|
|mbean:className|MBean class name|
|mbean:objectName|MBean object name|
|mbean properties|separate property for each property of the object name|
And a child resource named _mbean:attributes_ if the MBean has attributes.
For each attribute a child resource of _mbean:attributes_ is created where
the name of the resource is the name of the attribute and:
||Property name ||Description|
|sling:resourceType|Type of the attribute|
|sling:resourceSuperType| sling:mbeanattribute|
|mbean:description|The description of the attribute (optional)|
|mbean:value|String representation of the value or a string array for multi
values|
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (SLING-2999) JMX Resource Provider
[ https://issues.apache.org/jira/browse/SLING-2999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13734854#comment-13734854 ] Carsten Ziegeler commented on SLING-2999: - On the other hand, is there a problem with using mbeans: ? As this is not a jcr backed resource provider, we don't need to register the namespace in the repository JMX Resource Provider - Key: SLING-2999 URL: https://issues.apache.org/jira/browse/SLING-2999 Project: Sling Issue Type: New Feature Reporter: Carsten Ziegeler Assignee: Carsten Ziegeler For easier rendering of JMX mbeans within Sling, a special resource provider should make the JMX information available at */system/sling/monitoring/mbeans* (Configurable) /system/sling/monitoring/mbeans - resource type = sling:mbeans + resource sub tree with all mbeans An MBean has an object name which has * a domain * properties where type and name are very common The domain is converted into a sub path and the properties are converted to a resource name. For example: _org.apache.sling:name=test,type=hello_ creates a resource _org/apache/sling/name=test,type=hello_. The name can be obtained by calling _ObjectName.getCanonicalKeyPropertyListString()_. The result might need escaping (for the values and the = character) in order to create valid resource names. Each MBean resource has at least: ||Property name ||Description| |sling:resourceType|object name of the MBean| |sling:resourceSuperType| sling:mbean| |mbean:description|The description of the MBean (optional)| |mbean:className|MBean class name| |mbean:objectName|MBean object name| |mbean properties|separate property for each property of the object name| And a child resource named _mbean:attributes_ if the MBean has attributes. For each attribute a child resource of _mbean:attributes_ is created where the name of the resource is the name of the attribute and: ||Property name ||Description| |sling:resourceType|Type of the attribute| |sling:resourceSuperType| sling:mbeanattribute| |mbean:description|The description of the attribute (optional)| |mbean:value|String representation of the value or a string array for multi values| -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (SLING-2999) JMX Resource Provider
[ https://issues.apache.org/jira/browse/SLING-2999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13734904#comment-13734904 ] Carsten Ziegeler commented on SLING-2999: - I've added a stub for the implementation in rev 1512336 JMX Resource Provider - Key: SLING-2999 URL: https://issues.apache.org/jira/browse/SLING-2999 Project: Sling Issue Type: New Feature Reporter: Carsten Ziegeler Assignee: Carsten Ziegeler For easier rendering of JMX mbeans within Sling, a special resource provider should make the JMX information available at */system/sling/monitoring/mbeans* (Configurable) /system/sling/monitoring/mbeans - resource type = sling:mbeans + resource sub tree with all mbeans An MBean has an object name which has * a domain * properties where type and name are very common The domain is converted into a sub path and the properties are converted to a resource name. For example: _org.apache.sling:name=test,type=hello_ creates a resource _org/apache/sling/name=test,type=hello_. The name can be obtained by calling _ObjectName.getCanonicalKeyPropertyListString()_. The result might need escaping (for the values and the = character) in order to create valid resource names. Each MBean resource has at least: ||Property name ||Description| |sling:resourceType|object name of the MBean| |sling:resourceSuperType| sling:mbean| |mbean:description|The description of the MBean (optional)| |mbean:className|MBean class name| |mbean:objectName|MBean object name| |mbean properties|separate property for each property of the object name| And a child resource named _mbean:attributes_ if the MBean has attributes. For each attribute a child resource of _mbean:attributes_ is created where the name of the resource is the name of the attribute and: ||Property name ||Description| |sling:resourceType|Type of the attribute| |sling:resourceSuperType| sling:mbeanattribute| |mbean:description|The description of the attribute (optional)| |mbean:value|String representation of the value or a string array for multi values| -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (SLING-2999) JMX Resource Provider
[ https://issues.apache.org/jira/browse/SLING-2999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13731716#comment-13731716 ] Felix Meschberger commented on SLING-2999: -- I like this. But why introduce a new namespace mbean ? To prevent collisions with the ObjectName properties ? Could this be solved without a namespace ? JMX Resource Provider - Key: SLING-2999 URL: https://issues.apache.org/jira/browse/SLING-2999 Project: Sling Issue Type: New Feature Reporter: Carsten Ziegeler Assignee: Carsten Ziegeler For easier rendering of JMX mbeans within Sling, a special resource provider should make the JMX information available at */system/sling/monitoring/mbeans* (Configurable) /system/sling/monitoring/mbeans - resource type = sling:mbeans + resource sub tree with all mbeans An MBean has an object name which has * a domain * properties where type and name are very common The domain is converted into a sub path and the properties are converted to a resource name. For example: _org.apache.sling:name=test,type=hello_ creates a resource _org/apache/sling/name=test,type=hello_. The name can be obtained by calling _ObjectName.getCanonicalKeyPropertyListString()_. The result might need escaping (for the values and the = character) in order to create valid resource names. Each MBean resource has at least: ||Property name ||Description| |sling:resourceType|object name of the MBean| |sling:resourceSuperType| sling:mbean| |mbean:description|The description of the MBean (optional)| |mbean:className|MBean class name| |mbean:objectName|MBean object name| |mbean properties|separate property for each property of the object name| And a child resource named _mbean:attributes_ if the MBean has attributes. For each attribute a child resource of _mbean:attributes_ is created where the name of the resource is the name of the attribute and: ||Property name ||Description| |sling:resourceType|Type of the attribute| |sling:resourceSuperType| sling:mbeanattribute| |mbean:description|The description of the attribute (optional)| |mbean:value|String representation of the value or a string array for multi values| -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (SLING-2999) JMX Resource Provider
[ https://issues.apache.org/jira/browse/SLING-2999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13731747#comment-13731747 ] Bertrand Delacretaz commented on SLING-2999: Looks good to me, this will be useful to access health check MBeans as per SLING-2987 JMX Resource Provider - Key: SLING-2999 URL: https://issues.apache.org/jira/browse/SLING-2999 Project: Sling Issue Type: New Feature Reporter: Carsten Ziegeler Assignee: Carsten Ziegeler For easier rendering of JMX mbeans within Sling, a special resource provider should make the JMX information available at */system/sling/monitoring/mbeans* (Configurable) /system/sling/monitoring/mbeans - resource type = sling:mbeans + resource sub tree with all mbeans An MBean has an object name which has * a domain * properties where type and name are very common The domain is converted into a sub path and the properties are converted to a resource name. For example: _org.apache.sling:name=test,type=hello_ creates a resource _org/apache/sling/name=test,type=hello_. The name can be obtained by calling _ObjectName.getCanonicalKeyPropertyListString()_. The result might need escaping (for the values and the = character) in order to create valid resource names. Each MBean resource has at least: ||Property name ||Description| |sling:resourceType|object name of the MBean| |sling:resourceSuperType| sling:mbean| |mbean:description|The description of the MBean (optional)| |mbean:className|MBean class name| |mbean:objectName|MBean object name| |mbean properties|separate property for each property of the object name| And a child resource named _mbean:attributes_ if the MBean has attributes. For each attribute a child resource of _mbean:attributes_ is created where the name of the resource is the name of the attribute and: ||Property name ||Description| |sling:resourceType|Type of the attribute| |sling:resourceSuperType| sling:mbeanattribute| |mbean:description|The description of the attribute (optional)| |mbean:value|String representation of the value or a string array for multi values| -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (SLING-2999) JMX Resource Provider
[
https://issues.apache.org/jira/browse/SLING-2999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13731771#comment-13731771
]
Carsten Ziegeler commented on SLING-2999:
-
Yes, the namespace is there do avoid collision with potentially existing
properties. The properties are already contained in the object name, so we
could go without them, thus avoiding the use of a namespace. I don't have a
concrete use case for needing the object name properties as properties of the
mbean resource, but if we need them later on, we would need some separation.
The only alternative I see is to prefix the property names which is kind of a
namespace but not in the jcr sense, like property-{name}
JMX Resource Provider
-
Key: SLING-2999
URL: https://issues.apache.org/jira/browse/SLING-2999
Project: Sling
Issue Type: New Feature
Reporter: Carsten Ziegeler
Assignee: Carsten Ziegeler
For easier rendering of JMX mbeans within Sling, a special resource provider
should make the JMX information available at
*/system/sling/monitoring/mbeans* (Configurable)
/system/sling/monitoring/mbeans - resource type = sling:mbeans
+ resource sub tree with all mbeans
An MBean has an object name which has
* a domain
* properties where type and name are very common
The domain is converted into a sub path and the properties are converted to a
resource name. For example: _org.apache.sling:name=test,type=hello_ creates a
resource _org/apache/sling/name=test,type=hello_. The name can be obtained by
calling _ObjectName.getCanonicalKeyPropertyListString()_. The result might
need escaping (for the values and the = character) in order to create valid
resource names.
Each MBean resource has at least:
||Property name ||Description|
|sling:resourceType|object name of the MBean|
|sling:resourceSuperType| sling:mbean|
|mbean:description|The description of the MBean (optional)|
|mbean:className|MBean class name|
|mbean:objectName|MBean object name|
|mbean properties|separate property for each property of the object name|
And a child resource named _mbean:attributes_ if the MBean has attributes.
For each attribute a child resource of _mbean:attributes_ is created where
the name of the resource is the name of the attribute and:
||Property name ||Description|
|sling:resourceType|Type of the attribute|
|sling:resourceSuperType| sling:mbeanattribute|
|mbean:description|The description of the attribute (optional)|
|mbean:value|String representation of the value or a string array for multi
values|
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
