[ https://issues.apache.org/jira/browse/CASSANDRA-12312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15406184#comment-15406184 ]
T Jake Luciani commented on CASSANDRA-12312: -------------------------------------------- Great thanks, I'll commit this soon. > Restore JVM metric export for metric reporters > ---------------------------------------------- > > Key: CASSANDRA-12312 > URL: https://issues.apache.org/jira/browse/CASSANDRA-12312 > Project: Cassandra > Issue Type: Bug > Reporter: Stefan Podkowinski > Assignee: Stefan Podkowinski > Labels: lhf > Fix For: 2.2.x, 3.0.x, 3.x > > Attachments: 12312-2.2.patch, 12312-3.0.patch, 12312-trunk.patch, > metrics-jvm-3.1.0.jar.asc > > > 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}}). -- This message was sent by Atlassian JIRA (v6.3.4#6332)