[
https://issues.apache.org/jira/browse/CASSANDRA-9448?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14620159#comment-14620159
]
Stefan Podkowinski commented on CASSANDRA-9448:
-----------------------------------------------
As already mentioned by Nick, changing metric names will break monitoring
solutions. Users would have to reconfigure dashboards and reports. As a
consequence this also makes comparing performance between 2.x and 3.x more
cumbersome as you have to switch between the old and new naming scheme. It also
makes it hard to compare historical performance data between the effected
metrics.
I'd rather suggest to create a new config option for this. By default,
Cassandra would use the new naming. Users, who need to use the old metric
names, can switch back in the config.
See patch
([diff|https://github.com/apache/cassandra/compare/trunk...spodkowinski:feat/9448-newmetricnames])
for very simple implementation.
> Metrics should use up to date nomenclature
> ------------------------------------------
>
> Key: CASSANDRA-9448
> URL: https://issues.apache.org/jira/browse/CASSANDRA-9448
> Project: Cassandra
> Issue Type: Improvement
> Components: Tools
> Reporter: Sam Tunnicliffe
> Assignee: Stefania
> Labels: docs-impacting, jmx
> Fix For: 3.0 beta 1
>
>
> There are a number of exposed metrics that currently are named using the old
> nomenclature of columnfamily and rows (meaning partitions).
> It would be good to audit all metrics and update any names to match what they
> actually represent; we should probably do that in a single sweep to avoid a
> confusing mixture of old and new terminology.
> As we'd need to do this in a major release, I've initially set the fixver for
> 3.0 beta1.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
