Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-57909

JMX: VM and System metrics shouldn't be exported

    XMLWordPrintable

Details

    • 4.0.2.5

    Description

      Currently, all metrics are exported through JMX.

      For VM and System metrics, it doesn't make sense, because they are already exported through standard JMX MBeans such as java.lang:Memory and java.lang:OperatingSystem

      For historical metrics, it doesn't make sense to export them as typically the APM softwares (DataDog, Prometheus, Elasticsearch, Splunk, AppDynamics...) that will connect through JMX have their own time series database and will compute the historical data by themselves.

       

      Attachments

        Issue Links

          Activity

            vlatombe Vincent Latombe created issue -
            vlatombe Vincent Latombe made changes -
            Field Original Value New Value
            Description Currently, all metrics are exported through JMX.

            For VM and System metrics, it doesn't make sense, because they are already exported through standard JMX MBeans such as *java.lang:Memory* and *java.lang:OperatingSystem*

             
            Currently, all metrics are exported through JMX.

            For VM and System metrics, it doesn't make sense, because they are already exported through standard JMX MBeans such as *java.lang:Memory* and *java.lang:OperatingSystem*

            For historical metrics, it doesn't make sense to export them as typically the APM softwares that will connect through JMX have their own time series database and will compute the historical data by themselves.

             
            vlatombe Vincent Latombe made changes -
            Description Currently, all metrics are exported through JMX.

            For VM and System metrics, it doesn't make sense, because they are already exported through standard JMX MBeans such as *java.lang:Memory* and *java.lang:OperatingSystem*

            For historical metrics, it doesn't make sense to export them as typically the APM softwares that will connect through JMX have their own time series database and will compute the historical data by themselves.

             
            Currently, all metrics are exported through JMX.

            For VM and System metrics, it doesn't make sense, because they are already exported through standard JMX MBeans such as *java.lang:Memory* and *java.lang:OperatingSystem*

            For historical metrics, it doesn't make sense to export them as typically the APM softwares (DataDog, Prometheus, Elasticsearch, Splunk, AppDynamics...) that will connect through JMX have their own time series database and will compute the historical data by themselves.

             
            vlatombe Vincent Latombe made changes -
            Assignee Vincent Latombe [ vlatombe ]
            vlatombe Vincent Latombe made changes -
            Status Open [ 1 ] In Progress [ 3 ]
            vlatombe Vincent Latombe made changes -
            Status In Progress [ 3 ] In Review [ 10005 ]
            vlatombe Vincent Latombe made changes -
            Remote Link This issue links to "PR #48 (Web Link)" [ 23103 ]

            Thank you vlatombe for your contribution!

            alecharp Adrien Lecharpentier added a comment - Thank you vlatombe for your contribution!
            alecharp Adrien Lecharpentier made changes -
            Released As 4.0.2.5
            Resolution Fixed [ 1 ]
            Status In Review [ 10005 ] Resolved [ 5 ]

            How do you collect for example vm.blocked.count metric since 4.0.2.5 ? It is not exposed in standard JMX Mbeans

            brainsam Alexander Moiseenko added a comment - How do you collect for example vm.blocked.count metric since 4.0.2.5 ? It is not exposed in standard JMX Mbeans

            People

              vlatombe Vincent Latombe
              vlatombe Vincent Latombe
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: