[
https://issues.apache.org/jira/browse/CASSANDRA-15582?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17077714#comment-17077714
]
David Capwell commented on CASSANDRA-15582:
-------------------------------------------
bq. Analysis of that fashion through my experimental script is more of a
one-time test however and I wasn't sure if there was some intent based on these
comments to more fully automate this sort of testing going forward to help
avoid breaking metric changes as part of the standard and ongoing testing
process. I'd be curious what the direction is in this area and I'm happy to try
to help.
In my opinion automation is great, but I am also fine with incremental
improvements. If we had a documented way to collect all metrics, we can
eventually improve this to be an automated thing which generates a report of
what metrics exist, and with that we could diff with previous results. If the
very first deliverable is not automated (circle ci or Jenkins running) I am
totally ok with this.
bq. Assuming I haven't missed something important, this initial body of
analysis seems to indicate that there isn't widespread breaking change in JMX
for 4.x. I'm still staring at all this to determine what else might be tested
or if I've missed something important in this initial work.
Possible to print out what was added and what was removed?
bq. I'm happy to hear if any of this is interesting or helpful (or if I'm on
the completely wrong track to what is desired here). If not, I'll assume I
should just continue on this track of analysis and continue to post findings.
This does look promising. A good way to test this would be to cause a
regression and see if you catch it! But overall the idea makes sense.
I am curious the results for all prefixes, I spun up a cluster and see the
following
!Screen Shot 2020-04-07 at 5.47.17 PM.png!
> 4.0 quality testing: metrics
> ----------------------------
>
> Key: CASSANDRA-15582
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15582
> Project: Cassandra
> Issue Type: Task
> Components: Test/dtest
> Reporter: Josh McKenzie
> Assignee: Romain Hardouin
> Priority: Normal
> Fix For: 4.0-rc
>
> Attachments: Screen Shot 2020-04-07 at 5.47.17 PM.png
>
>
> In past releases we've unknowingly broken metrics integrations and introduced
> performance regressions in metrics collection and reporting. We strive in 4.0
> to not do that. Metrics should work well!
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
