[CASSANDRA-12312] Restore JVM metric export for metric reporters

• Type: Bug
• Status: Resolved
• Priority: Normal
• Resolution: Fixed
• Fix Version/s: 2.2.8, 3.0.9, 3.8
• Labels: lhf
• Severity: Normal
• Assignee: Stefan Podkowinski
• Reporter: Stefan Podkowinski

Authors

Stefan Podkowinski

Reviewers

T Jake Luciani

• Created: 27/Jul/16 07:43
• Updated: 16/Apr/19 09:30
• Resolved: 05/Aug/16 15:56

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).

Issue Links

• is broken by: CASSANDRA-5657 Upgrade metrics lib and remove deprecated metrics