You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@cassandra.apache.org by "David Capwell (Jira)" <ji...@apache.org> on 2020/08/28 16:18:00 UTC

[jira] [Commented] (CASSANDRA-16082) Add a new jmxtool which can dump what JMX objects exist and diff

    [ https://issues.apache.org/jira/browse/CASSANDRA-16082?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17186649#comment-17186649 ] 

David Capwell commented on CASSANDRA-16082:
-------------------------------------------

I took [~spmallette] groovy code and turned it into a tool we can run in CI.

> 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: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org