Thanks a lot guys!
I have a feeling that this tool will give me hell. 😈
I'll just have to wait till they implement it and monitor the clusters, but
at least I know what to expect.
Thanks again
On Tue, Nov 17, 2020 at 1:33 AM Jeff Jirsa wrote:
> (Just to put this in perspective, it's probabl
(Just to put this in perspective, it's probably a 10-20x increase in
writes, depending on how many replicas you're using, and your read:write
mix. Most people who use tracing do so probabilistically, with p < 1)
On Mon, Nov 16, 2020 at 2:09 PM Erick Ramirez
wrote:
> I wouldn't do it. It will sig
I wouldn't do it. It will significantly affect the performance of your
cluster so your monitoring ends up killing the very thing it's monitoring.
Perhaps you could tell us what outcome you're after so we'd be able to
offer a better solution. Like audit logging, for example. Cheers!
>
Tracing fully on rather than sampling will definitely add substantial load,
even with shorter TTLs. That's a lot of extra writes.
If it's just on for specific sessions, or is enabled but with low sampling,
that's not bad in terms of load.
On Mon, Nov 16, 2020 at 6:25 AM Shalom Sagges
wrote:
>
Hi Guys,
Our Service team would like to add a 3rd party tool (AppDynamics) that will
monitor Cassandra.
This tool will get read permissions on the system_traces keyspace and also
needs to enable TRACING.
tracetype_query_ttl in the yaml file will be reduced from 24 hours to 5
minutes.
I feel and fe
