Uploaded image for project: 'Cassandra'
  1. Cassandra
  2. CASSANDRA-12312

Restore JVM metric export for metric reporters

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Normal
    • Resolution: Fixed
    • Fix Version/s: 2.2.8, 3.0.9, 3.8
    • Component/s: None
    • Labels:
    • Severity:
      Normal

      Description

      JVM instrumentation as part of dropwizard metrics has been moved to a separate metrics-jvm artifact in metrics-v3.0. After CASSANDRA-5657, no jvm related metrics will be exported to any reporter configured via metrics-reporter-config, as this isn't part of metrics-core anymore. As memory and GC stats are essential for monitoring Cassandra, this turns out to be a blocker for us for upgrading to 2.2.

      I've included a patch that would add the now separate metrics-jvm package and enables some of the provided metrics on startup in case a metrics reporter is used (-Dcassandra.metricsReporterConfigFile).

        Attachments

        1. 12312-2.2.patch
          54 kB
          Stefan Podkowinski
        2. 12312-3.0.patch
          53 kB
          Stefan Podkowinski
        3. metrics-jvm-3.1.0.jar.asc
          0.5 kB
          Stefan Podkowinski
        4. 12312-trunk.patch
          57 kB
          Stefan Podkowinski

          Issue Links

            Activity

              People

              • Assignee:
                spod Stefan Podkowinski
                Reporter:
                spod Stefan Podkowinski
                Authors:
                Stefan Podkowinski
                Reviewers:
                T Jake Luciani
              • Votes:
                0 Vote for this issue
                Watchers:
                5 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: