Thanks Allen, This works, is there any documentation that explain about all the available logging levels?
On Fri, Sep 6, 2019 at 12:07 AM Jai Bheemsen Rao Dhanwada < jaibheem...@gmail.com> wrote: > Thanks, I will try that. > > Is this changed between 2.1.16 to 3.11.3? > > On Thursday, September 5, 2019, Inquistive allen <inquial...@gmail.com> > wrote: > >> Hello Jai, >> >> If you want to fetch queries from the logs. >> >> Kindly run the below command: >> >> nodetool setlogginglevel org.apache.cassandra.transport TRACE >> >> this will help you see all your queries in logs. >> Just beware that this fills up logs really fast. >> >> Thanks, >> Allen >> >> On Fri, 6 Sep, 2019, 10:57 AM Jai Bheemsen Rao Dhanwada, < >> jaibheem...@gmail.com> wrote: >> >>> Hello, >>> >>> I am trying to enable debug logs on the Cassandra cluster running with >>> 3.11.3, I do see some debug logs but I don't see the same level of DEBUG >>> logs I used to see with 2.1.16 version of cassandra. >>> >>> I am using the below command to set debug logging. >>> >>> $ nodetool setlogginglevel org.apache.cassandra DEBUG >>> >>> >>> In the 2.1.16 version of Cassandra I see the below logs when I make a >>> select query using CQL, but I don't see the same trace logs in 3.11.3. has >>> anything changed in the 3.11.3 version? >>> >>>> DEBUG [SharedPool-Worker-1] 2019-09-06 03:43:10,593 Message.java:437 - >>>> Received: QUERY SELECT * FROM ks.cf WHERE key=? AND id=?;, v=3 >>> >>> >>> Thanks in advance. >>> >>
