I think you are looking for this:
https://docs.datastax.com/en/developer/java-driver/2.1/manual/logging/#logging-query-latencies
You can use com.datastax.driver.core.QueryLogger.NORMAL /SLOW /ERROR to see
the queries executed. We are using only slow & error logs in production.
Normal is good for d
I don't know if it you help you, but when the debug log is turned on, it
displays the slow queries.
To consider slow, the parameter read_request_timeout_in_ms is considered.
Maybe if you decrease it, you can monitor your queries, with $tail -F
debug.log
Just an idea, I've never made it. Surely it
Hi Community,
Can anyone help me understand what class's id need to set logging on , if I
want to capture the cql commands being run through the driver, similar to how
profiler (MSSQL) would work? I need to see what's being run, and if the query
is actually getting to cassandra?
Has anyone had
