[
https://issues.apache.org/jira/browse/CASSANDRA-9448?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14616885#comment-14616885
]
Nick Bailey commented on CASSANDRA-9448:
----------------------------------------
This will certainly break some monitoring tools, OpsCenter for sure. If the
only solution that allows deprecating the old metrics is to duplicate them,
then perhaps that is too much overhead and the monitoring tools out there will
just have to take that hit, but it would be great to avoid. I also don't know
of a way to 'alias' things with the metrics library though.
> 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)
