You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@karaf.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2017/07/06 16:08:00 UTC

[jira] [Commented] (KARAF-5239) JMX collector doesn't full harvest metrics

    [ https://issues.apache.org/jira/browse/KARAF-5239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16076808#comment-16076808 ] 

ASF subversion and git services commented on KARAF-5239:
--------------------------------------------------------

Commit b00abb2fb472e586a636b791577e99aca8e32501 in karaf-decanter's branch refs/heads/master from [~jbonofre]
[ https://git-wip-us.apache.org/repos/asf?p=karaf-decanter.git;h=b00abb2 ]

[KARAF-5239] Fix JMX collector when no object.name are specified.


> JMX collector doesn't full harvest metrics
> ------------------------------------------
>
>                 Key: KARAF-5239
>                 URL: https://issues.apache.org/jira/browse/KARAF-5239
>             Project: Karaf
>          Issue Type: Bug
>          Components: decanter
>            Reporter: Jean-Baptiste Onofré
>            Assignee: Jean-Baptiste Onofré
>            Priority: Blocker
>             Fix For: decanter-1.4.0
>
>
> Even if the Karaf scheduler periodically calls the JMX collector:
> {code}
> 2017-07-06T16:38:28,602 | DEBUG | null_Worker-2    | JmxCollector                     | 119 - org.apache.karaf.decanter.collector.jmx - 1.4.0.SNAPSHOT | Karaf Decanter JMX Collector starts harvesting jmx-local...
> 2017-07-06T16:38:28,602 | DEBUG | null_Worker-2    | JmxCollector                     | 119 - org.apache.karaf.decanter.collector.jmx - 1.4.0.SNAPSHOT | Harvesting local MBeanServer (jmx-local)...
> 2017-07-06T16:38:28,603 | DEBUG | null_Worker-2    | JmxCollector                     | 119 - org.apache.karaf.decanter.collector.jmx - 1.4.0.SNAPSHOT | Karaf Decanter JMX Collector harvesting jmx-local done
> {code}
> However, we don't see JMX metrics in the storage backend. I'm checking why.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)