[
https://issues.apache.org/jira/browse/CASSANDRA-18155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17681200#comment-17681200
]
Caleb Rackliffe commented on CASSANDRA-18155:
---------------------------------------------
The CircleCI config was generated by a tool [~dcapwell] wrote that just
segregates J8 and J11, and then cleans up the targets that aren’t run anyway
from the report. (We’ve been using it for quite a while.) The issue of the
wrongly identified repeats needs another look. I messed one of these up
recently when my clone’s trunk branch wasn’t up-to-date w/ upstream trunk, so
it might have been that. Hopefully I can figure it out in the morning…
> Coordinator level metrics for read response and mutation row and column counts
> ------------------------------------------------------------------------------
>
> Key: CASSANDRA-18155
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18155
> Project: Cassandra
> Issue Type: Improvement
> Components: Observability/Metrics
> Reporter: Caleb Rackliffe
> Assignee: Caleb Rackliffe
> Priority: Normal
> Fix For: 4.x
>
> Time Spent: 4.5h
> Remaining Estimate: 0h
>
> We propose creating a new metric group, {{ClientRequestSize}}, that will
> house 4 new coordinator-level metrics:
> 1.) ColumnsRead - the total number of columns returned from the database to
> clients
> 2.) RowsRead - the total number of rows returned from the database to clients
> 3.) ColumnsWritten - the total number of columns written to the database by
> clients
> 4.) RowsWritten - the total number of rows written to the database by clients
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
