[ https://issues.apache.org/jira/browse/CASSANDRA-13000?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16213520#comment-16213520 ]
Jeff Jirsa commented on CASSANDRA-13000: ---------------------------------------- [~rustyrazorblade] - as the reporter, are you interested in reviewing? > slow query log analysis tool > ---------------------------- > > Key: CASSANDRA-13000 > URL: https://issues.apache.org/jira/browse/CASSANDRA-13000 > Project: Cassandra > Issue Type: New Feature > Components: Observability > Reporter: Jon Haddad > Assignee: Murukesh Mohanan > Fix For: 4.0 > > Attachments: > 0001-Adds-a-cqldumpslow-tool-which-analyses-the-debug-log.patch, > 0001-Adds-a-cqldumpslow-tool-which-analyses-the-debug-log.patch, > csqldumpslow.py > > > As a follow up to CASSANDRA-12403, it would be very helpful to have a tool to > process the slow queries that are logged. In the MySQL world, there's a tool > called mysqldumpslow, which processes a slow query log, abstracts the > parameters to prepared statements, and shows the queries which are causing > problems based on frequency. The {{mysqldumpslow}} utillity shows an > aggregated count & time statistics spent on slow queries. For instance: > {code}shell> mysqldumpslow > Reading mysql slow query log from > /usr/local/mysql/data/mysqld51-apple-slow.log > Count: 1 Time=4.32s (4s) Lock=0.00s (0s) Rows=0.0 (0), root[root]@localhost > insert into t2 select * from t1 > Count: 3 Time=2.53s (7s) Lock=0.00s (0s) Rows=0.0 (0), root[root]@localhost > insert into t2 select * from t1 limit N > Count: 3 Time=2.13s (6s) Lock=0.00s (0s) Rows=0.0 (0), root[root]@localhost > insert into t1 select * from t1{code} -- This message was sent by Atlassian JIRA (v6.4.14#64029) --------------------------------------------------------------------- To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org