We used to have monitoring scripts that parsed the output of nodetool (status,
listsnapshots), but these tools have been replaced with using Jolokia (REST
interface to JMX) — this is both more powerful and easier to parse for things
like monitoring scripts. We *really* would have loved to have
I am sorry, this is the correct link
https://lists.apache.org/thread/72j5qfgbttjcmylhcmfq1ptboh641ns0
From: Miklosovic, Stefan
Sent: Wednesday, July 12, 2023 0:08
To: user@cassandra.apache.org
Subject: Re: Survey about the parsing of the tooling's output
...@cassandra.apache.org
From: Andrew Weaver
Sent: Monday, July 10, 2023 17:37
To: user@cassandra.apache.org
Subject: Re: Survey about the parsing of the tooling's output
You don't often get email from andrewjwea...@gmail.com. Learn why this is
important<ht
+1 to Bowen Song's feedback for the most part.
We have processes that parse output from these nodetool commands:
- info
- netstats
- status
- version
My opinion is that for anyone running a reasonably sized fleet of Cassandra
will have different flavors of automation - some things
7:25 AM
To: user@cassandra.apache.org
Subject: [EXTERNAL] Re: Survey about the parsing of the tooling's output
We parse the output of the following nodetool sub-commands in our custom
scripts: status netstats tpstats ring We don't mind the output format change
between major releases as long
We parse the output of the following nodetool sub-commands in our custom
scripts:
* status
* netstats
* tpstats
* ring
We don't mind the output format change between major releases as long as
all the following are true:
1. major releases are not too frequent
e.g. no more frequent
