Thanks Laxmikant and Paul.
@Laxmikant, Unfortunately, this cluster is still on 2.1 so ECAudit won't
support it, but will check it out once it's upgraded to 3.x (should happen
pretty soon).
@Paul, I will definitely try the Wireshark method.
Thanks a lot guys for your help!
On Thu, Sep 26, 2019
Hi Shalom,
When tracking down specific queries I have used ngrep and fed the results into
Wireshark, this will allow you to find out everything about the requests coming
into the node from the client, as long as the connection is not encrypted.
I wrote this up here a few months ago:
One of the way to figure out what queries have run is to use audit
logging plugin supported in 3.x, 2.2
https://github.com/Ericsson/ecaudit
On Thu, Sep 26, 2019 at 2:19 PM shalom sagges
wrote:
> Thanks for the quick response Jeff!
>
> The EXECUTE lines are a prepared statement with the
Thanks for the quick response Jeff!
The EXECUTE lines are a prepared statement with the specified number of
parameters.
Is it possible to find out on which keyspace/table these prepared
statements run?
Can I get additional information from the prepared statement's ID? e.g.
EXECUTE
The EXECUTE lines are a prepared statement with the specified number of
parameters.
On Wed, Sep 25, 2019 at 11:38 PM shalom sagges
wrote:
> Hi All,
>
> I've been trying to find which queries are run on a Cassandra node.
> I've enabled DEBUG and ran *nodetool setlogginglevel
>
Hi All,
I've been trying to find which queries are run on a Cassandra node.
I've enabled DEBUG and ran *nodetool setlogginglevel
org.apache.cassandra.transport TRACE*
I did get some queries, but it's definitely not all the queries that are
run on this database.
I've also found a lot of DEBUG
