[
https://issues.apache.org/jira/browse/CASSANDRA-15582?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17106324#comment-17106324
]
Stephen Mallette commented on CASSANDRA-15582:
----------------------------------------------
> How do we ensure that all code paths that generate the metrics are exercised?
>> I think this was a good point as well. I've yet to come across a metric that
>> wasn't initialized as start of cassandra
After a bit of digging it seems that there are a number of metrics that don't
simply initialize as a result of cassandra starting up successfully.
* Streaming Metrics
* HintedHandoff Metrics
* HintsService Metrics
* Batch Metrics
It's also worth noting that certain metric scopes don't seem to initialize on
startup, specifically: ThreadPools. As a result there a number of missing
metrics to evaluate.
It seems that to cover everything we'd need to fire some sort of "metric
initialization" script prior to gathering metrics for analysis/testing. I guess
I will start researching how best to do that. Of course, my knowledge of what's
missing comes from the documentation being compared to the results of my jmx
scripts so if there is a metric not in the docs AND also not initialized at
cassandra start, I don't know how to uncover that except by way of digging
through code.
> 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-beta
>
> 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: [email protected]
For additional commands, e-mail: [email protected]
