Re: Log application Queries

2018-06-05 Thread Luigi Tagliamonte
I implemented an audit query handler that archives the queries in ES here: https://github.com/ltagliamonte/cassandra-audit PRs are welcome! On Mon, May 28, 2018 at 1:55 AM, Horia Mocioi wrote: > Hello, > > Another way to do it would be to create your own QueryHandler: > >- create a class

Re: Log application Queries

2018-05-28 Thread Horia Mocioi
Hello, Another way to do it would be to create your own QueryHandler: * create a class that would implement the QueryHandler interface and make Cassandra aware of it * in that class you can maintain a list of the queries (add to this list when prepare method is being called) and the

Re: Log application Queries

2018-05-25 Thread Nitan Kainth
this is awesome Jeff. Regards, Nitan K. Cassandra and Oracle Architect/SME Datastax Certified Cassandra expert Oracle 10g Certified On Fri, May 25, 2018 at 3:00 PM, Jeff Jirsa wrote: > https://issues.apache.org/jira/browse/CASSANDRA-13983 was added to > cassandra 4.0 > > > >

Re: Log application Queries

2018-05-25 Thread Jeff Jirsa
https://issues.apache.org/jira/browse/CASSANDRA-13983 was added to cassandra 4.0 On Fri, May 25, 2018 at 8:24 AM, Nitan Kainth wrote: > Hi, > > I would like to log all C* queries hitting cluster. Could someone please > tell me how can I do it at cluster level? > Will

Re: Log application Queries

2018-05-25 Thread Nitan Kainth
Thanks Alain Regards, Nitan K. Cassandra and Oracle Architect/SME Datastax Certified Cassandra expert Oracle 10g Certified On Fri, May 25, 2018 at 2:05 PM, Alain RODRIGUEZ wrote: > Nate wrote a post about this exact topic. In case it is of some use: >

Re: Log application Queries

2018-05-25 Thread Alain RODRIGUEZ
Nate wrote a post about this exact topic. In case it is of some use: http://thelastpickle.com/blog/2016/02/10/locking-down-apache-cassandra-logging.html C*heers, --- Alain Rodriguez - @arodream - al...@thelastpickle.com France / Spain The Last Pickle - Apache Cassandra

Re: Log application Queries

2018-05-25 Thread Nitan Kainth
So settraceprobability is better option than nodetool :) Regards, Nitan K. Cassandra and Oracle Architect/SME Datastax Certified Cassandra expert Oracle 10g Certified On Fri, May 25, 2018 at 12:15 PM, Surbhi Gupta wrote: > nodeool setlogginglevel is only valid for

Re: Log application Queries

2018-05-25 Thread Surbhi Gupta
nodeool setlogginglevel is only valid for below : - org.apache.cassandra - org.apache.cassandra.db - org.apache.cassandra.service.StorageProxy On 25 May 2018 at 09:01, Nitan Kainth wrote: > Thanks Surbhi. I found another way. I used nodetool

Re: Log application Queries

2018-05-25 Thread Nitan Kainth
Thanks Surbhi. I found another way. I used nodetool settraceprobability 1 and it is logging in system_traces. How is it different from nodeool setlogginglevel? Regards, Nitan K. Cassandra and Oracle Architect/SME Datastax Certified Cassandra expert Oracle 10g Certified On Fri, May 25, 2018 at

Re: Log application Queries

2018-05-25 Thread Surbhi Gupta
If using dse then u can enable in dse.yaml. # CQL slow log settings cql_slow_log_options: enabled: true threshold_ms: 0 ttl_seconds: 259200 As far as my understanding says setlogginglevel is used for changing the logging level as below but not for slow query . - ALL - TRACE - DEBUG

Log application Queries

2018-05-25 Thread Nitan Kainth
Hi, I would like to log all C* queries hitting cluster. Could someone please tell me how can I do it at cluster level? Will nodetool setlogginglevel work? If so, please share example with library name. C* version 3.11