Jaydeepkumar Chovatia created CASSANDRA-14527: -------------------------------------------------
Summary: Real time Bad query logging framework Key: CASSANDRA-14527 URL: https://issues.apache.org/jira/browse/CASSANDRA-14527 Project: Cassandra Issue Type: New Feature Components: Observability Reporter: Jaydeepkumar Chovatia Assignee: Jaydeepkumar Chovatia Fix For: 4.0 If Cassandra is not used in right way then it can create adverse effect to the application. There are lots of bad queries when using Cassandra, but major problem is end user don’t know where and what exactly is the problem. Most of the times end user is ready to take actions on bad queries provided Cassandra gives all detailed which could have potential impact on cluster performance. There has been already lots of work done as part of CASSANDRA-12403, proposal as part of this JIRA is let’s have some common way of detecting and logging different problems in Cassandra cluster which could have potential impact on Cassandra cluster performance. Please visit this document which has details like what is currently available, motivation behind developing this common framework, architecture, samples, etc. [https://docs.google.com/document/d/1D0HNjC3a7gnuKnR_iDXLI5mvn1zQxtV7tloMaLYIENE/edit?usp=sharing] Here is the patch with this feature: ||trunk|| |[!https://circleci.com/gh/jaydeepkumar1984/cassandra/tree/bqr.svg?style=svg! |https://circleci.com/gh/jaydeepkumar1984/cassandra/78]| |[patch |https://github.com/apache/cassandra/compare/trunk...jaydeepkumar1984:bqr]| Please review this doc and the patch, and provide your opinion and feedback about this effort. Thank you! -- This message was sent by Atlassian JIRA (v7.6.3#76005) --------------------------------------------------------------------- To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org