[ https://issues.apache.org/jira/browse/CASSANDRA-14572?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17792797#comment-17792797 ]
Maxim Muzafarov commented on CASSANDRA-14572: --------------------------------------------- However, the left alignment looks more eye-friendly. Here is the issue to provide some options for users: CASSANDRA-19150 {code:bash} cqlsh> select * from system_views.metrics_dropped_message; name | scope | type | value -------------------------------------------------------------------------------------------------------+-----------------------------------+-------+------- org.apache.cassandra.metrics.DroppedMessage.CrossNodeDroppedLatency.BATCH_REMOVE_REQ | BATCH_REMOVE_REQ | timer | 0 org.apache.cassandra.metrics.DroppedMessage.CrossNodeDroppedLatency.BATCH_REMOVE_RSP | BATCH_REMOVE_RSP | timer | 0 org.apache.cassandra.metrics.DroppedMessage.CrossNodeDroppedLatency.BATCH_STORE_REQ | BATCH_STORE_REQ | timer | 0 org.apache.cassandra.metrics.DroppedMessage.CrossNodeDroppedLatency.BATCH_STORE_RSP | BATCH_STORE_RSP | timer | 0 org.apache.cassandra.metrics.DroppedMessage.CrossNodeDroppedLatency.CLEANUP_MSG | CLEANUP_MSG | timer | 0 org.apache.cassandra.metrics.DroppedMessage.CrossNodeDroppedLatency.COUNTER_MUTATION_REQ | COUNTER_MUTATION_REQ | timer | 0 org.apache.cassandra.metrics.DroppedMessage.CrossNodeDroppedLatency.COUNTER_MUTATION_RSP | COUNTER_MUTATION_RSP | timer | 0 org.apache.cassandra.metrics.DroppedMessage.CrossNodeDroppedLatency.DATA_MOVEMENT_EXECUTED_REQ | DATA_MOVEMENT_EXECUTED_REQ | timer | 0 org.apache.cassandra.metrics.DroppedMessage.CrossNodeDroppedLatency.DATA_MOVEMENT_EXECUTED_RSP | DATA_MOVEMENT_EXECUTED_RSP | timer | 0 org.apache.cassandra.metrics.DroppedMessage.CrossNodeDroppedLatency.ECHO_REQ | ECHO_REQ | timer | 0 org.apache.cassandra.metrics.DroppedMessage.CrossNodeDroppedLatency.ECHO_RSP | ECHO_RSP | timer | 0 org.apache.cassandra.metrics.DroppedMessage.CrossNodeDroppedLatency.FAILED_SESSION_MSG | FAILED_SESSION_MSG | timer | 0 {code} > Expose all table metrics in virtual table > ----------------------------------------- > > Key: CASSANDRA-14572 > URL: https://issues.apache.org/jira/browse/CASSANDRA-14572 > Project: Cassandra > Issue Type: New Feature > Components: Legacy/Observability, Observability/Metrics > Reporter: Chris Lohfink > Assignee: Maxim Muzafarov > Priority: Low > Labels: virtual-tables > Fix For: 5.x > > Time Spent: 10m > Remaining Estimate: 0h > > While we want a number of virtual tables to display data in a way thats great > and intuitive like in nodetool. There is also much for being able to expose > the metrics we have for tooling via CQL instead of JMX. This is more for the > tooling and adhoc advanced users who know exactly what they are looking for. > *Schema:* > Initial idea is to expose data via {{((keyspace, table), metric)}} with a > column for each metric value. Could also use a Map or UDT instead of the > column based that can be a bit more specific to each metric type. To that end > there can be a {{metric_type}} column and then a UDT for each metric type > filled in, or a single value with more of a Map<Text, Text> style. I am > purposing the column type though as with {{ALLOW FILTERING}} it does allow > more extensive query capabilities. > *Implementations:* > * Use reflection to grab all the metrics from TableMetrics (see: > CASSANDRA-7622 impl). This is easiest and least abrasive towards new metric > implementors... but its reflection and a kinda a bad idea. > * Add a hook in TableMetrics to register with this virtual table when > registering > * Pull from the CassandraMetrics registery (either reporter or iterate > through metrics query on read of virtual table) -- 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