You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Chetan Mehrotra (JIRA)" <ji...@apache.org> on 2016/12/13 06:36:58 UTC
[jira] [Closed] (SLING-5443) Review the naming conventions used by
JMXReporter to register the Metric MBeans
[ https://issues.apache.org/jira/browse/SLING-5443?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Chetan Mehrotra closed SLING-5443.
----------------------------------
> Review the naming conventions used by JMXReporter to register the Metric MBeans
> -------------------------------------------------------------------------------
>
> Key: SLING-5443
> URL: https://issues.apache.org/jira/browse/SLING-5443
> Project: Sling
> Issue Type: Improvement
> Components: Commons
> Reporter: Chetan Mehrotra
> Assignee: Chetan Mehrotra
> Labels: docs-impacting
> Fix For: Commons Metrics 1.2.0
>
>
> With current setup the JMXReporter would register all metrics under {{org.apache.sling}} domain. [~pfaffm@adobe.com] suggested that this can cause confusion as metrics registered by non Sling bundle would also show up in Sling JMX domain.
> We should customize the JMX ObjectName logic to account for bundle which has registered the metrics. One approach that can be used is
> # Expose the MetricService as a ServiceFactory
> # Use some custom Bundle header else fallback to Bundle Symbolic name
> Discussion thread on mailing list http://markmail.org/thread/sj6yvmyhgze6jn22
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)