[
https://issues.apache.org/jira/browse/CASSANDRA-16082?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17186661#comment-17186661
]
Stephen Mallette commented on CASSANDRA-16082:
----------------------------------------------
interesting. I think that ultimately some sort of workload needs to be executed
prior to doing the jmx tests to make sure that all the metrics are actually
initialized. iirc there were definitely a few that were documented that i never
managed to see anywhere.
> Add a new jmxtool which can dump what JMX objects exist and diff
> ----------------------------------------------------------------
>
> Key: CASSANDRA-16082
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16082
> Project: Cassandra
> Issue Type: Improvement
> Components: Test/dtest/python
> Reporter: David Capwell
> Assignee: David Capwell
> Priority: Normal
>
> In order to help validate metric upgrade we first need to know what is new,
> what was removed, and what was changed. To help with this, we should add a
> new jmxtool which can dump the objects from JMX and diff them.
> Once we have this, we can also add a gold list of expected metrics and add
> tests to validate these metrics don’t change.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
