[
https://issues.apache.org/jira/browse/CASSANDRA-15582?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17056213#comment-17056213
]
Dinesh Joshi commented on CASSANDRA-15582:
------------------------------------------
Here's the outline of my plan. We should enumerate all metrics being published
in 3.0 and 3.11. We should verify if those metrics are present in 4.0 and if we
deviate from that list (and we will), we should document the difference.
Ideally, we should have some automated way of pulling all the metrics out so we
can detect changes in the list of published metrics in an automated way. Since
we publish all metrics via JMX, I think it is doable. Does this sound too
ambitious?
> 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
>
>
> 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: [email protected]
For additional commands, e-mail: [email protected]
